GuideMCP servers

An MCP security checklist for the servers already on your laptops

MCP servers arrive by copy and paste, run with the developer’s access and can change with any update. Here is what to check before, during and after one is approved.

By the NoFly team

Why MCP servers need their own review

An MCP server is code that an agent calls on its own. It usually runs on a laptop with the developer’s files, network and keys, and it describes its own tools to the model in plain language. That description is an instruction channel, and the server can change it in any release.

Before you approve one

  • Know who publishes it and where the code lives. A name on a registry is not an identity.
  • Pin a version. An unpinned server can change on its next launch.
  • Read the tool descriptions as instructions, because the model will.
  • Check which credentials it asks for, and give it the narrowest ones that work.
  • Run it first somewhere with no network and nothing to steal, and watch what it tries to reach.

While it runs

  • Route calls through a gateway, so tool lists, calls and results are screened in one place.
  • Keep the server’s credentials away from the agent itself.
  • Allow-list which agents may use which servers.
  • Record every call with the agent, the person and the result.

After it is approved

  • Watch for new versions, new tools and changed descriptions, and treat a change as a new review. Researchers call a server that changes after approval a rug pull.
  • Watch for a change of maintainer or repository.
  • Re-check installed servers when a new advisory or malicious package is published.
  • Remove servers nobody has called in weeks.

What has gone wrong already

A malicious npm package posing as a Postmark MCP server copied every email it sent to an outside address. A public GitHub issue steered an agent into leaking private repository data through the GitHub MCP server. Both would have passed a one-time look at the tool list.

How NoFly helps

  • Discover

    Every MCP server on laptops and in repositories is found and scanned in a sandbox with no network, then approved or denied, and watched for drift and for changing hands.

  • Protect

    One gateway screens tool lists, calls and results, withholds poisoned tool descriptions and keeps server credentials away from the agent.

  • Interrogate

    Live servers are questioned under controlled conditions, which catches a server that answers an agent differently from a scanner.

  • Govern

    An automation can quarantine a server the moment it changes after approval, and open a ticket for its owner.

What to do this week

This week3 actions
  1. Run npx @nofly/agent scan on one developer laptop and count the MCP servers.
  2. Pin every server to a version.
  3. Pick the server with the broadest credentials and narrow them this week.
Keep reading

More from the blog.

Find out what your AI is allowed to do today.

Book a call and we will map your agents, MCP servers and keys with you, or start on one laptop with the free scan.

Book a demo
npm i -g @nofly/agent