What to rip out before the MCP deprecation clock starts
After 2026-07-28, sticky sessions are already wrong — and Roots, Sampling, Logging, DCR, and legacy HTTP+SSE are on a twelve-month clock. Here is the stop-relying-on-X list.
Source: Influzer.ai
Spec 2026-07-28 did two different things at once: it made the protocol stateless now, and it started a formal twelve-month deprecation window for a pile of habits teams still ship.
Rip out immediately (not “when we get to it”):
- Sticky sessions /
Mcp-Session-Idassumptions - Servers that refuse traffic until
initializecompletes - Elicitation / sampling flows that need a held-open bidirectional stream (use MRTR instead)
Stop new adoption; schedule removal inside the twelve-month window:
- Roots, Sampling, Logging
- Legacy HTTP+SSE transport
- Dynamic Client Registration (move toward CIMD)
Why it matters: Claude, ChatGPT, and hosted agents already prefer ordinary HTTPS. Session-shaped infra will fail first under round-robin. Deprecated APIs will fail second — right when you are busiest.
Full operator checklist (30-day plan, auth hardening, header footguns): What to rip out before the deprecation clock hits. Browse remotes worth keeping in the directory.