MCP 2026-07-28 Specification (Stateless Core + Tasks)

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Evidence strength Strong

Decision

Human editorial judgment · 2026-06-28

Proceed with caution

Why: It is the canonical interop substrate we already build on, but the RC is an explicit breaking change with no compatibility shim; we want it, but only after validating our transport/lifecycle code against the RC during the ten-week window rather than chasing GA blind.
Next: Pin our MCP servers to 2025-11-25 in prod; spin up a non-prod 2026-07-28 RC branch to test stateless transport + per-request token validation against our existing session assumptions before the July 28 GA.

Constraints

No named blocker is present in the current public projection.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Initial public reading

This is the initial public reading. No earlier readiness change is recorded.