MCP Security & Configuration Auditor
Review an MCP server configuration for exposed secrets and risky permissions
- Runs in your browser
- Hard-coded credential detection
- Risky commands and transports
About MCP Security & Configuration Auditor
Paste a client configuration (an mcpServers or VS Code servers section), a single server definition, or the tools list a server returns, to check for hard-coded credentials, unpinned packages, shell wrappers, unencrypted endpoints, token passthrough settings and tool combinations that give a model more reach than it needs. Checks follow the 2026-07-28 revision of the Model Context Protocol specification. Nothing is executed and the configuration isn't uploaded.
What MCP configurations get wrong
A Model Context Protocol configuration decides which servers an AI client starts and what those servers can do. Common problems are easy to miss in a JSON file:
- API keys and database passwords written directly into the file
- Servers launched with npx without a pinned version
- Commands wrapped in a shell, or run from temporary directories
- Remote servers reached over plain HTTP
- Settings that pass user tokens straight through to a third-party server
Risky combinations
Individually reasonable tools can be dangerous together. A tool that reads local files plus one that makes outbound requests lets a prompt injection copy data out. The auditor maps what each server can do and flags combinations like this, even when each server looks fine on its own.
A static review
The auditor reads the configuration. It doesn’t start servers, call tools or connect to anything, so it can’t verify what a server really does. Credentials it finds are masked in the report; rotate any that were real.
Further reading
Questions people ask
- What inputs can I audit?
- A client configuration with a top-level mcpServers object or a VS Code servers object, a single server definition, or a tools, resources or prompts list, either on its own or as a full JSON-RPC response, in JSON or YAML.
- Which version of the MCP specification is used?
- Checks follow the 2026-07-28 revision, including its authorization guidance. The protocol version a configuration declares is shown in the report.
- Is my configuration uploaded?
- No. It’s analyzed in your browser and nothing is executed.