Your MCP Config Is the Actual Security Boundary. Nobody Audits It

说明与用途

mcp-audit 扫描 MCP 服务器配置，检测危险的 stdio 命令、未认证的端点、开放的绑定地址以及已知 CVE 版本，并可自动应用修复。

问题

MCP server configurations are hand‑edited JSON files that define the security boundary, yet existing scanners only lint design or flag risky patterns without checking for known CVEs or providing fixes.

结果

mcp-audit identifies and remediates critical security issues in MCP configs, such as unsafe stdio commands, unauthenticated endpoints, and vulnerable package versions, improving the security posture of locally run MCP servers.

工作流

• 1. Install the tool: pip install mcp-runtime-audit mcp-audit scan
• 2. Run a scan: mcp-audit scan (optionally with --probe to test endpoints)
• 3. Review findings in text or JSON output
• 4. Apply fixes: mcp-audit fix --apply (dry‑run with --dry-run first)
• 5. Optionally link agent‑guard: mcp-audit scan --link-agent-guard

证据

So I built mcp-audit — a local runtime security scanner for MCP servers with a bundled CVE table and one‑click fixes. stdlib only, no dependencies.

来源

Every finding carries a rule id, CVE id, severity, the evidence, and the fix — in text and JSON output, with CI‑ready exit codes (0 clean, 1 findings, 2 errors).

来源

The tool rewrites 0.0.0.0 → 127.0.0.1 in URLs, flags, and env values, adds an Authorization: Bearer ${MCP_TOKEN} placeholder to unauthenticated endpoints, backs up the config to <file>.bak‑<timestamp> before writing anything.

来源