Cloudflare (antidrift) MCP Server
@antidrift/mcp-cloudflare
npm
v0.22.0
Source verified
Published by probeo-io — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Cloudflare connector covering DNS, Pages, Workers, and R2.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Hardcoded egress to an external endpoint (bin/cli.mjs)MTC-SRC-003
In the server's implementation (`bin/cli.mjs:55`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { const res = await fetch('https://api.cloudflare.com/client/v4/user/tokens/verify', { headers: { 'Authorizati
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/cli.mjs
medium Hardcoded egress to an external endpoint (connectors/cloudflare.mjs)MTC-SRC-003
In the server's implementation (`connectors/cloudflare.mjs:8`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ) { const res = await fetch(`https://api.cloudflare.com/client/v4${path}`, { method, headers: { 'Authori
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server connectors/cloudflare.mjs
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.22.0 latest |
A 97/100 | 2 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @antidrift/mcp-cloudflare --onlineOther implementations of Cloudflare 9
Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →
Lets AI agents manage Cloudflare DNS records for your domains.
MCP server for managing Cloudflare DNS records across multiple domains from one API token
MCP server for cloudflare integration
Cloudflare’s official MCP server: manage Workers, KV, R2 and D1 from an assistant.
Slim Cloudflare server for DNS, zones, tunnels, WAF, and Zero Trust management via the Cloudflare v4 API.
MCP server for interacting with Cloudflare API
More in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.