MCP Guard
Static audit of your MCP server configuration.
The problem
MCP gives agents access to tools, files, and APIs — and most configs ship with plaintext tokens, auto-installed remote servers, and a filesystem server rooted at your home directory. One bad config line is a foothold.
What it does
Paste your claude_desktop_config.json or mcp.json and get a scored audit: plaintext secrets, unpinned remote installs (npx -y), shell pipes, and over-broad filesystem roots — each with a concrete fix. The config never leaves the request.
Capabilities
- Detects plaintext secrets embedded in server env
- Flags unpinned remote installs (supply-chain risk)
- Catches shell pipes / destructive command chains
- Flags filesystem servers rooted at / or $HOME
- Runs in the browser or as an npm package / CI gate
How you run it
Paste your config in the browser for a scored audit. Subscribers can install @playciso/mcpguard and fail CI on any high-severity finding.
Roadmap
- Static config audit + scoring
- In-browser audit form
- npm package + CI gate
- Runtime proxy: allow-lists + redaction
- Tamper-evident audit log
MCP Guard runs inside PlayCISO for subscribers. The source stays private — no public repos, nothing to fork, nothing for attackers to study. Weekly, monthly, and yearly plans all include every tool.