Cloudflare ended SSE on its product-specific MCP servers in a two-paragraph changelog entry. As of October 22 those servers serve only /mcp. A request to /sse returns 410 Gone with the server’s /mcp URL, “which most MCP clients show in their connection error.” Anyone configured with an /sse URL changes it, using https://docs.mcp.cloudflare.com/mcp as the pattern, and anyone who signed in through /sse signs in again. Connections already on /mcp are not affected.
There is no vendor number to discount here, and the short entry deserves credit for what it picks. A 410 says the old address is gone on purpose, which a 404 does not, and putting the replacement inside the failure means the fix travels to the person holding the broken configuration. That matters more for an MCP client than for most API consumers, because the person configuring a connector is often not a developer reading changelogs. The cost is stated too: re-authentication for anyone who came in through /sse. The one soft phrase is “most MCP clients.” A client that hides the error body leaves its user with a dead connector and no hint, and the entry does not say which clients those are.
This does not map cleanly to one API page, which is itself the useful finding. Cloudflare has 651 API pages in the catalog, and the three carrying MCP in their names, including the Cloudflare MCP Portal API, are portal surfaces rather than the product-specific servers this changelog names. So the retirement lands on a transport underneath the REST estate rather than on any contract in it. The agentic access profile records 5,254 operations, 2,628 of them acting and 106 human-in-the-loop.
The measurement confirms the pattern more than it challenges it. Cloudflare holds a Kin Score of 80.6, exemplar, and Agent Readiness of 72.5, agent-native, with the MCP server, error semantics, delegated identity, protected resource metadata and dynamic client registration dimensions all lit. A clean 410 is what a lit error semantics dimension looks like in practice. The weak spot sits elsewhere: contract governance is the lowest facet at 45.5, and the well-known catalog dimension is unlit. A server that tells you where it moved is good, and a published catalog would let a client learn the address before it ever needs the error.