MCP's largest revision reaches locked release candidate (spec 2026-07-28), governed under the Linux Foundation

Why it matters (spine). MCP is the connective tissue between agents and the world's tools and data. A stateless, extensible, LF-governed standard is the interface RDKG's machine customers will reach us through. Money angle: exposing verified ground truth as an MCP server (with Tasks for long-running verification jobs and MCP Apps for a citable UI) makes RDKG natively consumable by any compliant agent — the Machine Lane's front door. Metacrisis lever: verified data flowing to agents over a common, auditable, consent-gated protocol.

What would prove it wrong (falsifier). The final 2026-07-28 spec slips or fragments — major vendors ship incompatible forks, or Tier-1 SDKs miss the ten-week validation window — leaving no single interoperability standard for agents to converge on.

Live-status check + triangulation. RELEASE CANDIDATE, locked 21 May 2026 (version tag 2026-07-28 present in the draft specification); the FINAL spec is scheduled for 28 July 2026 and is NOT yet shipped as of today. The boring paper trail is deep: dozens of Specification Enhancement Proposal pull requests on github.com/modelcontextprotocol (e.g., SEP-2567 removes the session, SEP-2575 removes the handshake, SEP-2260 constrains server-initiated requests), plus the public draft spec and a changelog against 2025-11-25. The page footer ("Model Context Protocol a Series of LF Projects, LLC") confirms Linux Foundation stewardship; this is independently corroborated by the Linux Foundation's own reference to the "MCP Dev Summit North America" (2 Apr 2026) in its x402 press release, and by the public Wikipedia MCP entry and trade coverage. Primary is the first-party MCP maintainers' blog (authors: David Soria Parra, Den Delimarsky); spec text cited, not reproduced.

Correction — status update, 21 August 2026 (Standing Frontier Sweep, run 5). The live-status sentence above — "the FINAL spec is scheduled for 28 July 2026 and is NOT yet shipped as of today" — was true when written on 21 May 2026 and is no longer true. It is left in place rather than rewritten, per the ratchet rule that corrections are logged and not erased, and superseded here. Reading github.com/modelcontextprotocol/modelcontextprotocol/releases in session on 21 August 2026: the 2026-07-28 tag is published and marked Latest, released by localden at 28 Jul 16:47, with the release note "This release marks the stable release of the 2026-07-28 revision of the Model Context Protocol." The spec shipped on its named date. Two consequences for this card's falsifier, which has three limbs. The "slips" limb did not trigger. The fork limb and the Tier-1-SDK-conformance limb were not checked on 21 August and remain open — a published tag says nothing about whether major vendors ship incompatible forks. This also corrects the 31 July changelog, which parked the spec revision on a reading that its release milestone was still open at 80%; that reading is contradicted by the releases page. Downstream adoption is now carded separately at unreal-mcp-in-uefn-agentic-authoring (Epic Games, 20 August 2026).