Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Security scanner for AI coding agents, MCP servers, prompts, and AI-suggested packages.
Run it before Claude Code, Cursor, Windsurf, Cline, OpenCode, or another agent trusts new code, tools, prompts, or dependencies.
Scan any repo and get an A-F agent security grade:
Install the scanner into your AI coding client:
Replace claude-code with cursor, claude-desktop, windsurf, cline, kilo-code, opencode, or cody.
Audit an MCP server before adding it to an agent:
Check AI-generated imports for package hallucinations:
| Risk | Why agents need it | Command |
|---|---|---|
| Vulnerable generated code | Agents can introduce SQL injection, XSS, command injection, unsafe crypto, and secrets | scan-project, scan-security, scan-diff |
| MCP server attacks | MCP tools can poison descriptions, spoof names, exfiltrate env vars, or execute commands | scan-mcp |
| Prompt injection | Agents often process untrusted docs, tickets, pages, and tool output | scan-prompt |
| Unsafe agent actions | Catch dangerous shell/file/network actions before execution | scan-action |
| Hallucinated packages | AI often invents dependency names that attackers can later squat | check-package, scan-packages |
| SBOM and CVEs | Generate CycloneDX SBOMs and scan dependencies with OSV.dev | sbom-generate, sbom-vulnerabilities |
| Semantic review | LLM-powered review that uses project intent to find context-aware issues | cr-agent |
Run a safe local demo that creates intentionally vulnerable fixtures, scans them, and cleans them up.
Expected demo shape:
| Client | Setup |
|---|---|
| Claude Code | npx agent-security-scanner-mcp init claude-code |
| Cursor | npx agent-security-scanner-mcp init cursor |
| Claude Desktop | npx agent-security-scanner-mcp init claude-desktop |
| Windsurf | npx agent-security-scanner-mcp init windsurf |
| Cline | npx agent-security-scanner-mcp init cline |
| Kilo Code | npx agent-security-scanner-mcp init kilo-code |
| OpenCode | npx agent-security-scanner-mcp init opencode |
| Cody | npx agent-security-scanner-mcp init cody |
| Interactive picker | npx agent-security-scanner-mcp init |
Then restart the client. Your agent can call the scanner as an MCP tool.
Paste this into an agent task when you want it to work safely:
| Command | Use |
|---|---|
scan-project <dir> | Full project scan with A-F grade |
scan-security <file> | Single-file security scan |
scan-diff --base main --target HEAD | Scan changed files only |
scan-mcp <path> | Audit an MCP server before install |
scan-prompt "<text>" | Detect prompt injection and jailbreak attempts |
scan-action <type> <value> | Pre-execution safety check for shell/file/network actions |
check-package <name> <ecosystem> | Verify one package exists |
scan-packages <file> <ecosystem> | Verify imports/dependencies in a file |
doctor | Check local setup health |
quickstart --client cursor | Generate repo-specific next steps |
share-kit | Generate public-safe launch/share copy |
export-vanta | Export scan evidence to the ProofLayer Vanta integration |
All scanner outputs support context-friendly verbosity:
When installed as an MCP server, agents get these tool families:
| Tool family | Purpose |
|---|---|
scan_security, fix_security, scan_git_diff, scan_project | Code and repo security |
scan_mcp_server, scan_skill | MCP and AI skill security |
scan_agent_prompt, scan_agent_action | Prompt/action safety |
check_package, scan_packages | Package hallucination detection |
sbom_generate, sbom_scan_vulnerabilities, sbom_diff, sbom_export_report | Supply-chain and release evidence |
get_compliance_controls, evaluate_compliance | SOC2/GDPR/AIUC-1 technical evidence |
scanner_health | Runtime diagnostics |
npx command gives an A-F security grade for AI-written code.cr-agent is bundled with the npm package for LLM-powered semantic review. It reads project intent, then looks for code that violates that intent.
Use it when rule-based scanning is not enough and the question is, "Does this code make sense for what this project is supposed to do?"
Useful before releases, SOC 2 evidence collection, vendor reviews, and AI-generated dependency changes.
Run the scanner as an Apify Actor when you want a hosted API or scheduled scans:
v4.5.8 adds diff-scoped cr-agent semantic review, fixes nested repository diff lookups, and filters semantic findings to changed hunks so PR reviews stay focused on code that actually changed.
Detailed release history lives in CHANGELOG.md. The older README-embedded changelog is archived at archive/README_CHANGELOG_ARCHIVE.md.
Is this only for MCP servers? No. It scans normal repos, diffs, prompts, actions, packages, SBOMs, MCP servers, and AI skills.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/agent-security-scanner-mcp)<a href="https://allmcps.com/mcp/agent-security-scanner-mcp"><img src="https://allmcps.com/api/badge/agent-security-scanner-mcp?style=directory" alt="Agent Security Scanner MCP on AllMCPs" /></a>