MCP Scanner is a Python tool that examines Model Context Protocol servers and tools for security findings and potential threats. It can run as a command-line tool or REST API and uses YARA rules, LLM analysis, Cisco AI Defense, dependency checks, and other scans.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/cisco-ai-defense/mcp-scannerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/cisco-ai-defense/mcp-scanner/scan-static)<a href="https://agentmods.dev/commands/cisco-ai-defense/mcp-scanner/scan-static"><img src="https://agentmods.dev/badge/commands/cisco-ai-defense/mcp-scanner/scan-static/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/cisco-ai-defense/mcp-scanner/scan-static"><img src="https://agentmods.dev/badge/commands/cisco-ai-defense/mcp-scanner/scan-static.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.00360 |
| Opus 5 | $0.00008 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
scan-static scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Scan Static/Offline Files
Scan pre-generated MCP JSON files at "$ARGUMENTS" for security threats and risks. This mode is ideal for CI/CD pipelines, air-gapped environments, or reproducible security checks.
If the user provides a path, determine the file type and run the appropriate command:
For tools JSON file:
mcp-scanner --analyzers yara --format detailed static --tools "$ARGUMENTS"
For prompts JSON file:
mcp-scanner --analyzers llm --format detailed static --prompts "$ARGUMENTS"
For resources JSON file:
mcp-scanner --analyzers llm --format detailed static --resources "$ARGUMENTS"
For scanning multiple files at once:
mcp-scanner --analyzers yara,llm --format detailed static \
--tools /path/to/tools.json \
--prompts /path/to/prompts.json \
--resources /path/to/resources.json
If no path is provided, ask the user for:
- The path to the JSON file(s)
- What type of MCP data it contains (tools, prompts, or resources)
Expected JSON Format
{
"tools": [
{
"name": "tool_name",
"description": "Tool description",
"inputSchema": { "type": "object", "properties": {} }
}
]
}
For CI/CD pipelines, recommend using --analyzers yara --format summary for quick scans that don't require API keys.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 53 lines · 16 tokens per session scan A 2ffdf5cbf28f
scan-static is a command published in the GitHub repository cisco-ai-defense/mcp-scanner (1,066 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 360 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
template
Manage issue templates for streamlined issue creation.
discover
Search the Everruns(Dev) API catalog for available operations.
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
t800-onboard
A command for newcomers that explains what is installed in Cursor globally and in the current project, plus what the T-800 team can do.