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/nirhalfon/cinch-ai-security/cinch-ai-securitygit clone --depth 1 https://github.com/nirhalfon/cinch-ai-securityWrote 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/nirhalfon/cinch-ai-security/cinch-ai-security)<a href="https://agentmods.dev/mcp/nirhalfon/cinch-ai-security/cinch-ai-security"><img src="https://agentmods.dev/badge/mcp/nirhalfon/cinch-ai-security/cinch-ai-security.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cinch-ai-security 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 4d 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
Licensed CC-BY-4.0
The repository is licensed CC-BY-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 8 lines scan A 0b4f890704a7
cinch-ai-security is an MCP server published in the GitHub repository nirhalfon/cinch-ai-security (0 stars, last pushed 26d ago), licensed CC-BY-4.0. 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.
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.
kakunin
X.509 identity, risk scoring, and audit logging for AI agents. MiCA + EU AI Act compliant. Runs locally from the @kakunin/mcp npm package. Needs 2 environment variables to run.
nullsec-redteam-ai
MCP server "nullsec-redteam-ai" as configured in Panda1847/NullSec-RedTeam-AI. Runs locally from the nullsec-redteam-ai Python package.
hardened-mcp-server
MCP server "hardened-mcp-server" as configured in jkelly-dev1/hardened-mcp-server. Runs locally from the hardened-mcp-server Python package.