MCP 2026 Preview on the Governed Tool Gateway
The 2026-07-28 MCP specification modernizes agent transport. EmpowerID is previewing that wire on the same AuthZEN PEP—dual-era clients, honest maturity labels, no “certified” shortcuts.
Preview means wire and gateway behaviors under active test—not MCP Foundation WS9 “Passed” or a public “fully compliant MCP 2026” claim. Confirm scope for your edition and deployment with EmpowerID.
Why MCP 2026 matters to enterprises
Agents need a stable, inspectable transport: discover-first entry, Streamable HTTP, and OAuth resource-server behaviors such as issuer validation and structured insufficient-scope challenges. That is the handshake. Governance—delegation, schema discipline, credential modes without agent custody, receipts—is still the product.
Dual-era on one gateway
Legacy MCP clients and 2026 clients can target the same Governed Tool Gateway. AuthZEN policy on every tools/call does not fork by protocol year; only the transport slice differs.
What we say in public copy
- Preview for MCP 2026-07-28 transport features under test
- Live today: governed MCP PEP, ID-JAG consumption paths where deployed
- In progress: external MCP Foundation vendor conformance (WS9) before any “certified” label
What we do not claim
- “MCP 2026 certified” or “fully compliant” until WS9 Passed
- “EMA certified” as a product badge
- A single headline that merges MCP preview maturity with full XAA/ID-JAG parity across every IdP
For the standards matrix and MCP 2026 preview domain, see Standards and protocols. For product placement, see the Governed Tool Gateway page.
Related
Governed Tool Gateway →