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/ourobx/agent-ebpf/cloudflare-buildsgit clone --depth 1 https://github.com/ourobx/agent-ebpfWrote 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/ourobx/agent-ebpf/cloudflare-builds)<a href="https://agentmods.dev/mcp/ourobx/agent-ebpf/cloudflare-builds"><img src="https://agentmods.dev/badge/mcp/ourobx/agent-ebpf/cloudflare-builds.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cloudflare-builds 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 3d 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-builds": {
"url": "https://builds.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.
- 3d ago First seen · 5 lines scan A 176ee37fc29c
cloudflare-builds is an MCP server published in the GitHub repository ourobx/agent-ebpf (1 stars, last pushed 9d 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
pfsense-mcp
MCP server "pfsense-mcp" as configured in abl030/pfsense-mcp. Runs locally from the pfsense-mcp Python package.
ssh-licco
SSH Model Context Protocol Server - Enable SSH functionality for AI models. Runs locally from the ssh-licco Python package. Needs 4 environment variables to run.
tailscale-compute
Run builds, tests, and benchmarks on your own Tailscale compute node. Runs locally from the @dylantirandaz/tailscale-compute-mcp npm package. Needs 6 environment variables to run.
vmware-privateai
VMware Private AI Foundation with NVIDIA ops — GPU inventory, vGPU/DirectPath profiles, utilization, model-serving (MCP + CLI). Runs locally from the vmware-privateai Python package.
project-bourne
Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance. Runs locally from the @project-bourne/mcp npm package.
mcp
Massed Compute MCP — GPU inventory, VM lifecycle, billing, SSH keys, and setup recipes. Runs locally from the massed-compute-mcp npm package. Needs 1 environment variable to run.