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/danveil/mcp-security-inspectorWrote 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/mcp/danveil/mcp-security-inspector/mcp-tool-security-inspector)<a href="https://agentmods.dev/mcp/danveil/mcp-security-inspector/mcp-tool-security-inspector"><img src="https://agentmods.dev/badge/mcp/danveil/mcp-security-inspector/mcp-tool-security-inspector/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/mcp/danveil/mcp-security-inspector/mcp-tool-security-inspector"><img src="https://agentmods.dev/badge/mcp/danveil/mcp-security-inspector/mcp-tool-security-inspector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-tool-security-inspector 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
{ "mcp-tool-security-inspector": { "command": "uvx", "args": [ "mcp-tool-security-inspector" ] } }
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 · 8 lines scan A 9ab03686aba7
mcp-tool-security-inspector is an MCP server published in the GitHub repository danveil/mcp-security-inspector (1 stars, last pushed 12d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-31.
Other mcp servers, from other repositories
tooltrust-scanner
Scans MCP servers for prompt injection, data exfiltration, and privilege escalation. Runs locally from the tooltrust-mcp npm package.
mcp-safeguard
Security scanner for MCP servers — detect prompt injection, credential leaks, exposed endpoints, tool poisoning, and source-level credential-handling flaws. Runs locally from the mcp-safeguard Python package.
pkgxray
MCP server "pkgxray" as configured in adamsjack711-ux/pkgxray. Runs ./bin/mcp-server.js with node.
mcp-threatintel
Unified threat intel - OTX, AbuseIPDB, GreyNoise, abuse.ch, Feodo Tracker. Runs locally from the mcp-threatintel-server npm package. Needs 4 environment variables to run.
aegisforge
MCP server "aegisforge" as configured in sunilgentyala/AegisForge-MCP. Launched with cargo run --manifest-path mcp-server/Cargo.toml --release --. Needs 1 environment variable to run.
rocketcyber-mcp
MCP server "rocketcyber-mcp" as configured in WYRE-AI/rocketcyber-mcp. Runs in Docker (ghcr.io/wyre-ai/rocketcyber-mcp:v1.5.6). Needs 6 environment variables to run.