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/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/cloudflare-docs)<a href="https://agentmods.dev/mcp/louisbrulenaudet/monorepo-template/cloudflare-docs"><img src="https://agentmods.dev/badge/mcp/louisbrulenaudet/monorepo-template/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/louisbrulenaudet/monorepo-template/cloudflare-docs"><img src="https://agentmods.dev/badge/mcp/louisbrulenaudet/monorepo-template/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 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.
What it actually says
{
"cloudflare-docs": {
"type": "http",
"url": "https://docs.mcp.cloudflare.com/mcp"
}
}What else mcp.json configures
This page is one entry in a file that holds 3. 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.
- 1mo ago First seen · 6 lines scan A 10629e1b3eaa
cloudflare-docs is an MCP server published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed yesterday), 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-09-03.
Other mcp servers, from other repositories
refero
MCP server "refero", hosted remotely at api.refero.design, as configured in referodesign/referoskill.
davflare
MCP server "davflare", hosted remotely at drive.example.com, as configured in fanchenggang/Davflare.
mcp-gsc
Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics. Runs locally from the @digestseo/mcp-gsc npm package. Needs 4 environment variables to run.
hermes-pen-bridge
Hermes-first MCP bridge for the Pencil design tool — proxies the bundled MCP server and adds .pen file utilities. Runs locally from the hermes-pen-bridge Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.