MCP config checker
Paste the MCP configuration from Claude Code, Claude Desktop, Cursor or VS Code. Each server entry is a command that runs on your computer or an address your AI tool connects to; this checks them for the problems that are easy to miss in review, and says why each matters and how to fix it.
Runs in your browser. Nothing you type or paste leaves this page.
What it checks
- Unpinned package runners
- Servers started with npx, npm exec, pnpm dlx, bunx, uvx, uv tool run or pipx run without one exact version, or with @latest, and npx's -y flag, which installs without asking.
- Shell commands and downloads
- Servers that are a shell running a command string (bash -c, sh -c, PowerShell -Command, cmd /c), inline code, or a script downloaded and piped straight into a shell.
- Secrets in the file
- Credentials written into env, args, headers or the URL: values under names such as token, secret, password or api_key, and well-known token shapes. References such as ${VAR}, ${env:VAR} and ${input:id} are fine.
- Remote servers
- Plain http:// to anything other than this computer, and servers with no authentication header, which may still sign in with OAuth.
- Docker
- Images on :latest or without a tag, --privileged, the host's network or processes, and mounts of the whole disk, the home directory, system directories or the Docker socket.
- Filesystem access
- Filesystem servers, or any server, given / or the home directory.
- The file itself
- The same server name defined twice, the same name in more than one scope, VS Code inputs that are missing or don't hide what's typed, and a shape the tool doesn't recognise.
It reads the mcpServers object (Claude Code's .mcp.json and ~/.claude.json, Claude Desktop, Cursor) and VS Code's servers and inputs. A clean result means none of these checks matched, not that a server is safe: it can't see what a server's code does.
SpanDock's MCP gateway gives every computer's AI tools one MCP server and connects it, on your server, to your organisation's connectors. Connector credentials stay on the server, and each person gets only the connectors and tools they're allowed. It's on the Premium and Enterprise plans.
Sources
Each check relies on the vendors' own documentation, checked on 2026-10-22.
- Claude Code: connect Claude Code to tools via MCP (checked on 2026-10-22)
- Model Context Protocol: connect to local MCP servers (Claude Desktop) (checked on 2026-10-22)
- VS Code: MCP configuration reference (checked on 2026-10-22)
- Cursor: Model Context Protocol (checked on 2026-10-22)
- npm: npx (checked on 2026-10-22)
- pnpm: pnpm dlx (checked on 2026-10-22)
- Bun: bunx (checked on 2026-10-22)
- uv: using tools (checked on 2026-10-22)
- pipx: running applications (checked on 2026-10-22)
- Docker: docker container run (checked on 2026-10-22)
- Docker: security (daemon attack surface) (checked on 2026-10-22)
- GitHub: token formats (checked on 2026-10-22)
- Slack: token types (checked on 2026-10-22)
- IAM identifiers: unique ID prefixes (checked on 2026-10-22)