MCPSec – OWASP MCP Top Scanner for Model Context Protocol Configs
First MCP security scanner addressing early Docker Hub moment—but audience is still nascent.

MCP-specific guardrails when Claude ecosystem lacks native security scanning.
AI/LLM engineers, MCP server developers
LLM Guard · Lakera Guard · NeMo Guardrails
So I built a static analysis scanner specifically for MCP servers. It runs 7 analyzers (secrets, static code, prompt injection, SQL/command injection, permissions, network, dependencies) and takes ~45ms on a typical server.
Usage:
npx mcp-security-auditor scan ./my-mcp-server
No account, runs locally. Outputs text, JSON, SARIF (for GitHub Security tab), HTML, or Markdown. Has a CI mode that exits non-zero above a severity threshold.Available on both npm and PyPI. MIT licensed.
npm: https://www.npmjs.com/package/mcp-security-auditor PyPI: https://pypi.org/project/mcp-security-auditor/ Dev.to writeup with examples: https://dev.to/prabhu_raja_fe2261464cb8e/how-to-scan-your-mc...
Would love feedback on detection patterns — there are definitely gaps I haven't covered yet.
First MCP security scanner addressing early Docker Hub moment—but audience is still nascent.
Attack graph across MCP servers catches chains no single-server scanner finds; solves actual new problem.
First static analyzer for MCP servers catching command injection before you plug it in.
Think “Snyk for MCP configs”: Levenshtein-based typosquat detection, CVE lookups, hardcoded-credential scans and permission checks, plus CI-friendly exit codes. Auto-discovery for clients like Claude, Cursor and VS Code shows practical attention to workflows. It’s an early release — the value hinges on maintaining the package/CVE databases and tuning detection heuristics.
36 controls across MCP security domains, but is a checklist—not a tool, agent, or enforcement mechanism.
Semgrep for AI agents—138 rules, offline, catches obfuscated attacks other scanners miss.