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/CSOAI-ORG/iso-42005-impact-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/csoai-org/iso-42005-impact-mcp/iso-42005-impact-mcp)<a href="https://agentmods.dev/mcp/csoai-org/iso-42005-impact-mcp/iso-42005-impact-mcp"><img src="https://agentmods.dev/badge/mcp/csoai-org/iso-42005-impact-mcp/iso-42005-impact-mcp/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/csoai-org/iso-42005-impact-mcp/iso-42005-impact-mcp"><img src="https://agentmods.dev/badge/mcp/csoai-org/iso-42005-impact-mcp/iso-42005-impact-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
iso-42005-impact-mcp 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 11d 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
{
"iso-42005-impact-mcp": {
"command": "uvx",
"args": [
"iso-42005-impact-mcp"
]
}
}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.
- 11d ago First seen · 8 lines scan A 192cd5415e91
iso-42005-impact-mcp is an MCP server published in the GitHub repository CSOAI-ORG/iso-42005-impact-mcp (0 stars, last pushed 2mo 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
landlaw-ai-mcp
Landlaw Ai tools for AI agents. Capabilities: search land registry, check planning permission, explain covenant. Built by MEOK AI Labs. Runs locally from the landlaw-ai-mcp Python package.
license-checker-ai-mcp
MCP server for license checker ai. Features identify license, check compatibility, generate license. From MEOK AI Labs. Runs locally from the license-checker-ai-mcp Python package.
pci-dss-mcp
PCI DSS payment card industry compliance tools for AI agents. Capabilities: assess 12 requirements, cardholder data flow, network segmentation, vulnerability scans, SAQ generation. Built by MEOK AI Labs. Runs locally from the pci-dss-mcp Python package.
legal-document-ai-mcp
AI-powered legal document ai MCP server for agents. Supports generate nda, explain clause, define legal term. By MEOK AI Labs. Runs locally from the legal-document-ai-mcp Python package.
mcp-eu-ai-act
EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected. Remote server at mcp.arkforge.tech.
complyedge
Runtime EU AI Act deny for agent I/O (Article 5, Article 50) — ComplyEdge Python SDK. Runs locally from the complyedge Python package.