Repo Dossier
cloudflare/agents
MCP dependency surface as of . AgentScore reads this repo's package.json, .mcp.json, and .cursor/mcp.json, scans every MCP package found, and computes the same gate verdict the Policy Gate GitHub Action would return on a PR.
Files checked: package.json, .mcp.json
Get alerted when this repo's MCP stack changes
One confirmation email. Then alerts when any currently detected MCP package in cloudflare/agents changes score, risk, or capability surface.
Current package set: 1. New packages added later are not auto-included. This is best for the repo as it exists today, not as an always-on repo integration. Privacy: see /about.
The gate would pass every package
MCP packages in this repo
Aggregate capability surface
What powers an AI agent inherits by installing this repo's MCP stack.
- mediumunknownUnknown / unclassified
What changed in this MCP stack
Latest package-level drift across the MCP packages currently detected in this repo.
Version
v1.29.0 → v1.29.0
Score
100 → 100
Risk
LOW → LOW
Findings
0 → 0
Not covered by this scan
AgentScore scans npm packages. The items below use install paths the scanner cannot reach (remote HTTP, Python, Docker, raw git). Worth a manual review.
- agentshttps://agents.cloudflare.com/mcpRemote HTTP server (not an npm package)
Track this repo
Subscribe to the current MCP package set for cloudflare/agents. Use the email watch above for alerts, the filtered RSS feed for automation, or raw JSON if you want to poll the dossier directly.
The repo watch confirms the package set visible on this page. If the repo later adds new MCP packages, reopen the dossier and confirm the updated set.
Want this check to run on every PR?
Install the Policy Gate. One YAML block. Free for public repos. Auto-provisions via GitHub OIDC.