GOVERNED. STATELESS.
INEVITABLE.
On July 28, 2026, the Model Context Protocol undergoes its largest revision since launch. The session is gone. The handshake is gone. Every request stands alone. This is the moment AI tooling stops being a developer convenience and becomes institutional infrastructure. Infrastructure demands governance. Governance demands proof.
What the spec removed
The 2026-07-28 specification deleted the machinery that made MCP feel safe by accident. No more initialize handshake. No more session identifier. No more server-held session state (WorkOS). State now travels as handles the model passes back on every call (analysis), and the protocol runs on commodity HTTP, behind ordinary load balancers, at enterprise scale (StackPicks).
The blast radius at the protocol layer shrank. The responsibility at the implementation layer grew. Security researchers are direct about it: the stateless transition removes protocol-level risks and hands implementers new obligations around state, authorization, and control surfaces (Akamai analysis). The NSA's guidance on MCP security says enforcement must come from implementation rigor, not from the protocol itself (NSA CSI, May 2026).
The spec removed the session. It did not remove the accountability.
Someone has to hold it.
The gap every enterprise inherits on July 28
Your agents will call tools through stateless MCP. Any node. Any gateway. Any moment. Ask the questions your auditor will ask.
- Who authorized the call.
- What policy evaluated it.
- What evidence survived it.
- What proves the result delivered matches the result governed.
The protocol answers none of these. By design. That gap is not a feature request. It is an institutional liability, measured in regulatory exposure, board accountability, and trust.
Already live. Already governed.
ALEETH is not waiting for the deadline. The ALEETH Authority MCP runs the 2026-07-28 stateless specification in production today, published in the official MCP registry as com.aleeth/authority-mcp and independently graded A by the public spec scanner. Of more than four thousand reachable servers in the registry, it was the only one ready. And it is the only one governed.
See the proofThe ALEETH answer: governed stateless MCP
ALEETH built the control plane the protocol declined to include.
Rail Guard
The enforcement boundary. Every tool call is intercepted, risk-scored per principal, and authorized before it reaches a sensitive system. Quarantine latches until human review. Nothing waits out its own containment.
ALEETH Authority
The proof surface. Tool work executes only inside a live ICA governance context. Every successful result is sealed with a signed L7 receipt attesting to the full payload delivered, not a summary. What the auditor reads is what the agent received.
Receipts as the record of state
The stateless spec replaces sessions with state that travels call to call. ALEETH seals a signed receipt on every call, hash-chained to its lineage, and the full chain verifies against the public ledger, link by link, signature by signature.
The audit chain is not attached to the session.
The audit chain is the session.
No other architecture can make that claim.
The doctrine
- Fail closed.
- Malformed governance responses deny by default. Ambiguity is not authorization. No receipt, no response.
- Evidence before and after.
- Intent is recorded before a side effect. Receipts are sealed after. A crash leaves a reconciliation trail, not a hole.
- Per-principal accountability.
- Risk is scored by authenticated caller. No shared pools. No diluted attribution.
- Signed, chained, immutable.
- Ed25519 signatures. Canonical JSON. Hash-chained sequence. A hash without a signature is a note, not an attestation.
- Minimum necessary exposure.
- Tools are surfaced by capability tier, not by catalog. Curated surfaces are also faster surfaces: task-scoped tool exposure has been shown to cut token consumption by roughly 75% (Cyclr benchmark). Governance is the performance feature.
The window
The final specification ships July 28, 2026. Legacy versions enter a twelve-month deprecation window (Context Studios). Every enterprise deploying MCP behind its gateways inherits the governance gap the same day.
Most will discover it in an audit.
Yours does not have to.
AI has met its match. Truth.™
ALEETH built the Institutional Control Architecture.
ICA is its control fabric. Governed stateless MCP is what it proves.
Request the Authority briefing