MCP Goes Stateless, Agentic Traffic Now Detectable at Network Layer
The MCP 2026-07-28 specification's shift to a stateless, per-request model has made agentic traffic classifiable on the wire for the first time; and Cloudflare has shipped beta tooling to act on it. Businesses that publish through MCP servers or want AI agents to transact on their behalf now face a concrete infrastructure decision.
This Week's Signals
Cloudflare Gateway Beta Selector Makes MCP Traffic Visible and Blockable at Network Level
Why it matters for your score
The beta Gateway selector experimental.is_mcp == true lets enterprise networks classify agentic traffic by inspecting MCP-Protocol-Version, Mcp-Method, and Mcp-Name headers alongside JSON-RPC patterns; detection that was impossible under the old session-based model. For business owners, this means IT departments can now see and control which MCP servers employees or internal agents are calling, including unofficial ones. If your business runs an MCP server, expect enterprise clients to start auditing traffic flows to it through tooling like this.
Cloudflare Agents SDK v0.20.0 Confirms Stateless MCP Runs in a Single Worker With No Durable Objects
Why it matters for your score
Cloudflare confirmed in production with Sentry and Linear that MCP servers now run in a single Worker with no sticky sessions, open streams, or Durable Objects required, a meaningful cut in hosting complexity and cost. The SDK v0.20.0 auto-negotiates the new stateless protocol and falls back to the legacy handshake on the same connection, so migration does not require separate protocol settings. For any business building or maintaining an MCP server, this is the path to lower infrastructure overhead under the current spec.
What to do this week
- 1
Audit your site's existing content structure against the GEO-16 pillar criteria, headers, summary blocks, named data points, and clear entity attribution, since the Tokyo-Tsukuba study tied a 17.3% citation lift to structural changes alone, not content rewrites. Use Faro's /tools/ai-readiness-scan to identify which pages fall below threshold.
- 2
If you publish an MCP server, check whether your server implementation is compatible with the MCP 2026-07-28 stateless spec; Cloudflare's production confirmation with Sentry and Linear shows the migration is viable and reduces infrastructure requirements. Review your current session or Durable Object dependencies before enterprise clients begin filtering your traffic with tools like the Cloudflare Gateway selector.
- 3
Review your llms.txt and robots.txt files to confirm agentic crawlers are permitted to reach your highest-quality structured pages, the UC Berkeley data shows citation rates drop sharply below the GEO-16 quality threshold, so access blocks on well-structured pages are a direct visibility cost. Use Faro's /tools/llms-txt and /tools/robots-txt to check your current configuration.