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/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/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/yeodh10/security-mcp/security-tools"><img src="https://agentmods.dev/badge/mcp/yeodh10/security-mcp/security-tools.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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.
- 1mo 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 3mo 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
mcp-demo2
MCP server "mcp-demo2" as configured in vaibhavGala262/MCPservers. Runs locally from the mcp-demo2 Python package.
no_human
Autonomous AI software-delivery orchestrator driving the Claude Agent SDK on your own Claude credentials. Runs locally from the no-human Python package.
swiss-transport-mcp
MCP server for Swiss public transport – OJP journey planner, real-time departures, disruptions, occupancy, ticket prices, train formations and open data from opentransportdata.swiss. Runs locally from the swiss-transport-mcp Python package.
mcp-clickhouse
ClickHouse query & management for AI agents — SQL-classified read/write/destructive gating. Runs locally from the @dockndevai/mcp-clickhouse npm package. Needs 4 environment variables to run.
oraclemcp
MCP server "oraclemcp" as configured in MuhDur/oraclemcp. Runs in Docker (ghcr.io/muhdur/oraclemcp:0.9.0).
agent-magnet
Self-learning memory infrastructure for AI products. Runs locally from the agent-magnet Python package. Needs 6 environment variables to run.