There is no official Cloudflare MCP server in the registry.
As of the 2026-10-03 registry snapshot (38,152 indexed servers), no entry is published under a Cloudflare-owned namespace (com.cloudflare, io.github.cloudflare).
8 community servers use the Cloudflare name. None is published by Cloudflare; treat each as the third-party project it is.
- io.github.SidneyBissoli/senado-br-mcp-cloudflareupdated 2026-10-02
- io.github.pipeworx-io/cloudflare-radarupdated 2026-09-25
- io.github.ANAMIZED/x402-cloudflare-starterupdated 2026-08-23
- com.jojapi/cloudflare-solverupdated 2026-08-19
- com.jojapi/bypass-cloudflare-apiupdated 2026-08-19
- io.github.Evozim/cloudflare-turnstile-bypass-mcpupdated 2026-08-17
- io.github.pain2hustle/cloudflare-ops-mcpupdated 2026-08-17
- io.github.Ayo-Fam/mcp-cloudflare-dnsupdated 2026-06-30
The registry verifies namespace ownership, so a registered vendor entry is the one identity an agent can pin. Without one there is no verified Cloudflare namespace, no canonical entry to pin a tool contract against, and no drift history when the tool surface changes. A server using the name may still be useful; it is just not Cloudflare speaking.
How mcpindex evaluates what a server declares versus what it does is covered in the methodology and the trust model.
Publishing to the MCP registry gives your users a verifiable namespace. mcpindex syncs the registry daily; a published entry replaces this page with a normal server page, which you can then claim.