Check your MCP config for security problems

Paste your MCP configuration, or choose the file. It is checked in your browser for tokens written in it, servers that run whatever version is latest, plain-HTTP remotes and filesystem access that is too broad. Nothing is uploaded. Free, no account.

or paste it

Your config never leaves this page: the checks run in your browser. Open your browser's network tab to see for yourself.

Your config never leaves your browser

  1. The page brings the rules with it. They are part of this page, so nothing needs to be fetched to check your config.
  2. Your config is read and checked by this page's script, in your browser. Comments and trailing commas (common in editor configs) are fine.
  3. You get findings per server, a grade from A to F, and your config with every secret replaced by a ${NAME} placeholder, ready to copy.
  4. Only if you ask, the report is emailed: server names and rule ids, never the config. The server also refuses anything that looks like a key.

What we check

Where to find your MCP config file

Claude Desktop

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Settings › Developer › Edit Config opens it.

Claude Code

  • Project (shared): .mcp.json at the root of the repository
  • User and local scopes: ~/.claude.json

"claude mcp list" shows every server and where it comes from.

Cursor

  • Project: .cursor/mcp.json
  • Global: ~/.cursor/mcp.json

VS Code

  • Workspace: .vscode/mcp.json
  • User: the "MCP: Open User Configuration" command

VS Code uses a "servers" key and supports "inputs" for secrets.

Windsurf

  • All systems: ~/.codeium/windsurf/mcp_config.json

Gemini CLI

  • Project: .gemini/settings.json
  • User: ~/.gemini/settings.json

Servers are under "mcpServers".

Clients change these locations from time to time; check your client's documentation if a file is not where we say.

Safe MCP setup in five steps

  1. Keep secrets out of the file. Reference environment variables, or use your client's prompt or secret store.
  2. Pin every server to the version you reviewed: package@1.2.3, package==1.2.3 or an image tag or digest.
  3. Give each server the least access: one project folder, a read-only token, a scoped API key.
  4. Prefer servers published by the vendor of the service they connect to, over https, ideally with OAuth.
  5. Turn off what you don't use, per project: every server's tools are in every conversation.

Questions

Is my config uploaded?

No. The page downloads the rules and runs the checks in your browser; the config is never sent. If you ask for the report by email, only server names and the ids of the rules that matched are sent. You can check it in your browser's network tab.

Where is claude_desktop_config.json?

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%\Claude\claude_desktop_config.json. In Claude Desktop, Settings › Developer › Edit Config opens it.

Is it safe to put API keys in mcp.json?

It is risky: config files get committed, synced and shared, and every tool on your machine can read them. Reference an environment variable instead, or use your client's prompt or secret store, and rotate any key that was committed.

Should I pin MCP server versions?

Yes. "npx -y package" runs the newest release at every start, so a compromised or broken release reaches you without review. Pin the version you checked (package@1.2.3) and update on purpose.

What can an MCP server access?

Whatever its process can: a local server runs with your user's permissions and the environment variables you give it, plus the folders or accounts its own configuration allows. Its tools are offered to the model in every conversation.

How do I review a remote MCP server?

Check who runs it (prefer the vendor of the service it connects to), that it uses https, how it authenticates (OAuth is better than a token in the URL) and what it logs.

Last updated .