Cloudflare MCP servers stop serving /sse
Cloudflare product MCP servers now serve only /mcp. Requests to /sse return 410 Gone with the /mcp URL, and clients that signed in through /sse must sign in again. Reported 22 October 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare.
What it changes in the data held here
Of 817 reachable endpoints in the directory, 812 answered over Streamable HTTP and 5 over the legacy SSE transport. The 2026-07-28 specification classes SSE as deprecated, so the second figure is the count of servers that will need to move.
517 endpoints in the directory offer dynamic client registration, 16 publish OAuth metadata without a registration endpoint, and 191 state client ID metadata document support. 533 endpoints stop at a sign-in challenge, so this directory sees their auth route but not their tools.
Against the rule that an agent-ready product has an MCP server or a CLI, 263 directory companies have an MCP server with tools listed, 36 have a CLI on record and 1,044 have neither, out of 1,336.
Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal.
Source: developers.cloudflare.com, a primary source, dated 22 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026.
Where it shows up here
- Cloudflare: rubric and evidence
- Build a remote MCP server on Cloudflare or Vercel
- Keep an MCP server agent ready in CI
- Cloudflare in the directory: has an open MCP server with tools listed