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.
npx agentmods add mcp/yeodh10/security-mcp/security-toolsgit clone --depth 1 https://github.com/yeodh10/security-mcpWrote 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/yeodh10/security-mcp/security-tools)<a href="https://agentmods.dev/mcp/yeodh10/security-mcp/security-tools"><img src="https://agentmods.dev/badge/mcp/yeodh10/security-mcp/security-tools.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
security-tools 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 8 lines scan A 149d271eda4f
security-tools is an MCP server published in the GitHub repository yeodh10/security-mcp (0 stars, last pushed 2mo ago), with no licence file. 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
prometheus-mcp-server
MCP server "prometheus-mcp-server" as configured in pab1it0/prometheus-mcp-server. Runs in Docker (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2). Needs 14 environment variables to run.
mcptoon
Zero-setup MCP client for every AI agent. Sync MCP servers across agents. Token-efficient CLI: 99.8% less tokens on discovery. Zero deps. Runs locally from the mcptoon Python package.
servicenow
MCP server "servicenow" as configured in serac-labs/serac. Runs locally from the servicenow-mcp-stdio npm package.
seekstone
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax. Runs locally from the seekstone npm package. Needs 1 environment variable to run.
servicenow-mcp-ai
ServiceNow MCP server — 67 tools over the full REST surface, every auth method, flows, diagrams. Runs locally from the servicenow-mcp-ai npm package. Needs 6 environment variables to run.
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.