Review your MCP
setup risks.
ShieldMCP checks your configuration for permission risks, possible secrets, and supply chain warning signs. Static analysis is a starting point, not proof that your setup is safe.
Review configuration flags before connecting agents to sensitive systems.
Your config is sent to our server for static analysis. Use a sanitized copy under 50 KB: replace credentials with placeholders before uploading. This can affect secret-detection findings. Results are retained for seven days from scanning or starting checkout. Anyone with the scan URL can access the results, including paid details after unlock. Keep it private. Privacy and data retention
Drop your MCP config file here
or click to browse
Don't know where your config is? View guide
How it works
Three steps to a safer MCP setup.
Upload config
Drop your file or paste JSON. Supports claude_desktop_config.json, .cursor/mcp.json, and more.
Static analysis
Configuration checks mapped to OWASP MCP Top 10 categories. No account needed.
Fix issues
Review flagged issues. Unlock remediation guidance and config examples where available; test changes in your environment.
What we check
Static checks mapped to OWASP MCP Top 10 categories; runtime behavior is not tested.
Simple pricing
Start free. Unlock details when you need them.
Full Report
Per scan report
- Everything free +
- Remediation guidance
- Examples where available
- Priority order
- Shareable PDF
Pro
Coming soonPlanned features — not currently available. Pricing to be announced.
- Planned API access (CI/CD)
- Planned rescan alerts
- Planned scan history
- Planned team configs
- Planned Slack alerts
What a scan can tell you
Configuration flags help prioritize manual review. The scanner does not connect to your MCP servers, enumerate live tools, or verify effective permissions. A high score or a category with no flags does not establish safety. Review package sources and runtime behavior separately.