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/sherpa-sh/Sherpa-ActionWrote 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/sherpa-sh/sherpa-action/cloudflare-docs)<a href="https://agentmods.dev/mcp/sherpa-sh/sherpa-action/cloudflare-docs"><img src="https://agentmods.dev/badge/mcp/sherpa-sh/sherpa-action/cloudflare-docs/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/sherpa-sh/sherpa-action/cloudflare-docs"><img src="https://agentmods.dev/badge/mcp/sherpa-sh/sherpa-action/cloudflare-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cloudflare-docs 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
{
"cloudflare-docs": {
"command": "npx",
"args": [
"mcp-remote",
"https://docs.mcp.cloudflare.com/mcp"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 9 lines scan A a311c4ee3e05
cloudflare-docs is an MCP server published in the GitHub repository sherpa-sh/Sherpa-Action (22 stars, last pushed 7mo ago), licensed Apache-2.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-30.
Other mcp servers, from other repositories
flashcards
Read and write open-source flashcards through split read/write MCP tools. Remote server at mcp.flashcards-open-source-app.com.
terraform
MCP server "terraform" as configured in aws-samples/sample-agentic-chatbot-accelerator. Runs in Docker (hashicorp/terraform-mcp-server:0.5.2).
ai-guardian
Governed observability + governance for on-endpoint local LLMs (Ollama): model inventory/provenance, a deterministic secrets/PII/jailbreak prompt scanner, allow/deny policy, and route-through guarding — the complement to IGEL AI Armor, with a built-in governance harness (audit, budget, undo, risk tiers). Runs locally…
ceph-aiops
Governed AI-ops for Ceph (ceph-mgr Dashboard REST): HEALTHWARN root-cause analysis, OSD/PG/pool/RBD/CephFS/RGW operations, and destructive-op guardrails with a built-in governance harness (audit, budget, undo, risk tiers). Runs locally from the ceph-aiops Python package.
aws-auth
MCP server "aws-auth" as configured in N0mansky/aws-auth. Runs locally from the aws-auth Python package.
aws-audit-mcp
Read-only AWS security audit tools for AI agents, served over the Model Context Protocol. Runs locally from the aws-audit-mcp Python package.