About mcp-config-auditor
mcp-config-auditor is an MCP server for auditing MCP client configuration files and installed server inventories. It checks for risks such as unpinned packages, secrets, unsafe approvals, and server or skill conflicts without starting servers or transmitting scanned configuration by default.
Key features
- 01Audits Cursor, Claude Desktop, Windsurf, and VS Code configs
- 02Detects unpinned packages and container images
- 03Finds secrets and unsafe approval settings
- 04Checks remote access and cross-server tool conflicts
- 05Scans agent skills for risky permissions and instructions
- 06Discovers installed servers and compares allowlists
Use cases
- 01Reviewing MCP client configs for exposed credentials
- 02Checking server packages before running them
- 03Comparing installed servers with an organization allowlist
- 04Auditing skill files for unsafe permissions
MCP support
It exposes MCP configuration audit capabilities to MCP clients. Its CLI can scan configuration files or discover installed servers and compare them with an allowlist; it does not start those servers.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
6Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| label | string | No | Optional filename shown in findings |
| content | string | Yes | Raw JSON config |
Details
From the project README@guardbee/mcp-config-auditor
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
An MCP server that audits the MCP client config on a machine: Cursor mcp.json, Claude Desktop claude_desktop_config.json, Windsurf mcp_config.json, and VS Code mcp.json.
mcp-server-auditor reads an MCP server's source. This package reads the config that decides which servers an agent will run. It does not start those servers and it does not send the config anywhere.
Telemetry is off by default. With
GUARDBEE_TELEMETRY=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare replaced with a placeholder. See@guardbee/mcp-telemetry.
Claude ──► mcp-config-auditor ──► mcp.json (or host-wide discover)
│
├─ Unpinned package (npx -y pkg, @latest)
├─ Typosquat (one edit from a known server package)
├─ Secret in env/args
├─ autoApprove "*"
├─ Remote HTTP without auth
├─ Cross-server shadowing (when you pass a tool inventory)
├─ Agent SKILL.md (allowed-tools, body, lookalike names)
└─ Shadow MCP discover (OWASP MCP09 — host paths + org allowlist)
Checks
| Pattern | Severity | OWASP | What it means |
|---|---|---|---|
unpinned_package | high | MCP04:2025 | A launcher (npx, uvx, pnpm, yarn, bunx, pipx) runs a package with no major.minor.patch pin |
unpinned_container_image | high | MCP04:2025 | docker run / podman run starts an image by tag, not by @sha256: digest |
typosquat_package | critical | MCP04:2025 | The package name is one edit from a known MCP server package |
secret_in_env | critical | MCP01:2025 | A credential-shaped value or a sensitive key with a long literal |
secret_in_args | critical | MCP01:2025 | A token on the command line |
auto_approve_wildcard | critical | MCP02:2025 | autoApprove / alwaysAllow is * or true |
cleartext_remote | high | MCP07:2025 | A non-loopback http:// URL |
unauthenticated_remote | high/medium | MCP07:2025 | A non-loopback URL with no Authorization / API-key header and no token env var |
cross_server_tool_shadow | high | MCP03:2025 | The same tool name on two servers |
confusable_tool_name | critical | MCP03:2025 | Homoglyph or one-edit tool names across servers |
cross_server_tool_redirect | high | MCP03:2025 | A description tells the model to call another server's tool |
skill_unrestricted_shell | critical | MCP02:2025 | allowed-tools includes bare Bash, shell, or * |
skill_unrestricted_write | high | MCP02:2025 | allowed-tools includes Write or Edit with no path limit |
skill_instruction_override | critical | MCP06:2025 | The skill tells the model to ignore prior instructions |
skill_covert_instruction | critical | MCP06:2025 | The skill tells the model to hide its behavior from the user |
skill_secret_file_read | critical | MCP01:2025 | The skill tells the model to read .ssh, .env, or a similar file |
skill_at_secret_ref | critical | MCP01:2025 | An @ reference inlines a credential path |
secret_in_skill | critical | MCP01:2025 | A literal token is written in the skill file |
skill_name_shadow | high | MCP03:2025 | Two SKILL.md files use the same name |
skill_confusable_name | critical | MCP03:2025 | Two skill names differ only by a lookalike character |
shadow_mcp_server | high | MCP09:2025 | discover — server installed on the host but not on the org allowlist |
allowlist_not_configured | medium | MCP09:2025 | discover ran without an allowlist |
unreviewed_mcp_server | low | MCP09:2025 | Server seen during discover with no allowlist yet |
mcp_server_drift_across_clients | medium | MCP09:2025 | Same server key maps to different packages/URLs in two clients |
Loopback URLs (localhost, 127.0.0.1, ::1) are not remote findings. Placeholder values (${API_KEY}, changeme) are not secrets. Reported secret matches are redacted. Bash(git diff:*) is a command allowlist and is not an unrestricted shell. Read alone is not flagged.
Quick start
{
"mcpServers": {
"guardbee-mcp-config-auditor": {
"command": "npx",
"args": ["-y", "@guardbee/mcp-config-auditor"]
}
}
}
npx @guardbee/mcp-config-auditor scan .cursor/mcp.json --fail-on=high --format=sarif > results.sarif
npx @guardbee/mcp-config-auditor inventory ./tool-inventory.json
npx @guardbee/mcp-config-auditor discover --allowlist=./mcp-allowlist.json --fail-on=high
Shadow MCP discover (MCP09)
Walks well-known Cursor / Claude Desktop / Claude Code / Windsurf / VS Code / Gemini CLI / Cline / Zed paths on this machine and compares every installed server to an organization allowlist. Does not start servers. Claude Code's per-project servers (projects["<path>"].mcpServers in ~/.claude.json) are listed under claude-code:<path>; Zed's context_servers and JSON with comments are understood.
Inventory. --format=json adds an inventory: for every server its client, config path, name, transport, command and arguments, npm/PyPI package with version and whether it is pinned, URL, the names of its env variables and headers, auto-approve, and the findings for it. It never holds a secret: env and header values are left out, argument values after --token/--api-key-style flags, KEY=value pairs, provider tokens and passwords in connection strings are [redacted], and URLs lose their credentials and query values. --format=text prints the same list; --format=sarif the findings.
Organisation-wide. --upload sends the inventory to the GuardBee dashboard (GUARDBEE_API_KEY, a workspace key with the gateway.write scope), which keeps the latest inventory per machine; run it from your device-management tool or a login script. The machine's host name, OS and OS user name are included — --no-user leaves the user out.
GUARDBEE_API_KEY=gb_… npx @guardbee/mcp-config-auditor discover --allowlist=./mcp-allowlist.json --upload --fail-on=none
Allowlist JSON:
{
"names": ["filesystem", "github"],
"packages": ["@modelcontextprotocol/server-filesystem", "@guardbee/mcp-secret-scanner"],
"hosts": ["mcp.example.com"]
}
Or lines: name:filesystem, package:@scope/pkg, host:mcp.example.com, or a bare server name.
A directory scan opens mcp.json, mcp_config.json, claude_desktop_config.json, and SKILL.md. Pass a file path to scan any other name. A file named SKILL.md is audited as an agent skill. Same-name and lookalike skill findings appear on a directory scan, because one file cannot see the others.
guardbee.yml:
mcp-config-auditor:
fail-on: high
max-files: 5000
exclude:
- "fixtures/"
Tool inventory shape:
{
"servers": [
{ "name": "github", "tools": [{ "name": "create_issue", "description": "Open an issue" }] }
]
}
Shadowing needs that inventory because a client config does not list tools. rug-pull-detector can collect a live tools/list; this package compares several of those lists.
Feedback
Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a ⭐ on the repository helps others find it.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.