
Mcp Config Auditor
io.github.4hmetuyarPublished by GitHub account 4hmetuyarv0.3.1Updated Oct 24, 2026
Scans Cursor/Claude/Windsurf/VS Code MCP configs for unpinned versions, secrets, typosquats
Overview
Audits local MCP client configs (Cursor, Claude, Windsurf, VS Code) for unpinned packages, secrets, typosquats and risky auto-approve settings.
- What you can do
- Scan MCP client config files and directories for unpinned launchers, unpinned container images, typosquatted packages, secrets in env or args, wildcard auto-approve, and cleartext or unauthenticated remote URLs
- Audit agent SKILL.md files for unrestricted shell or write permissions, instruction overrides, covert instructions, secret reads and lookalike skill names
- Compare a supplied tool inventory across servers to flag duplicate, confusable or redirected tool names
- Discover servers installed across known client paths on the machine and compare them to an organization allowlist
- Produce an inventory of configured servers with client, path, transport, package pinning, env and header names…
- When to use it
- Useful when you want to check the MCP setup on a developer machine or fleet before trusting it: catching unpinned or lookalike packages, credentials written into configs, overly broad auto-approval, and servers that are not on an organization allowlist. Also handy for CI or device-management gating with a fail-on severity threshold.
- Requirements
- Runs locally over stdio, typically via npx with the published npm package; Node.js is needed. No credentials are required for scanning. Optional: GUARDBEE_API_KEY (workspace key with gateway.write scope) only for --upload, and an allowlist file for discover. The MCP Index is downloaded and cached locally unless --offline is used.
Installation
In SourceWeft
- Open Mcp Config Auditor in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@guardbee/mcp-config-auditor
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
[npm version] [npm downloads] [License: MIT]
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.
Checks
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
GuardBee MCP Index grades
--grades (on scan <file> and discover) shows the GuardBee MCP Index grade of every configured server: an A–F trust grade for each server in the official MCP Registry, rebuilt weekly from its published package. The grade comes from the shipped code (the GuardBee scanners), known vulnerabilities and malware (OSV), Sigstore build provenance and maintenance signals; the rubric is public and versioned. --min-grade=C also reports every server graded below C (mcp_index_grade_below_minimum, so --fail-on can gate on it).
The whole index is downloaded (and cached for a day in ~/.guardbee/mcp-index.json) and searched on this machine, so no server or package name is sent anywhere. --offline uses the cache only; --index-url= points at another copy. Local commands, remote URLs and servers outside the official registry have no grade and are never findings.
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.
Fleet. FLEET.md has Jamf, Intune, systemd and CI recipes. --allowlist-from-dashboard checks against the organization allowlist admins manage in the dashboard (merged with --allowlist when both are given), and --grades adds MCP Index grades to the uploaded inventory.
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.
Allowlist JSON:
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:
Tool inventory shape:
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.
Source: packages/mcp-config-auditor/README.md at commit fe7dc3a
Tools
0Version history
1- v0.3.1LatestSep 29, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
