Published , by The Key editors.
The July 2026 MCP specification and what it means for identity
In short: the 28 July 2026 MCP specification introduced a stateless core, header routing for gateways and CIMD in place of Dynamic Client Registration. It also formalised extensions, including Enterprise-Managed Authorization. Each change makes gateway enforcement and company-controlled authorization easier to run.
The Model Context Protocol published its specification update on 28 July 2026. For agent identity, the existing note identifies three central changes: a stateless core, header routing and CIMD. The update also formalised extensions, including Enterprise-Managed Authorization. These changes concern different parts of the access path and deserve separate consideration.
A stateless core makes it simpler to place a gateway in front of many servers. Header routing lets that gateway direct calls without inspecting every payload. Our recommendation is to examine routing and enforcement separately when reviewing a gateway design. Being able to direct a call is not the same question as deciding whether that call should proceed.
CIMD replaced Dynamic Client Registration. Clients identify themselves using a URL that hosts their metadata. The existing note describes this change as reducing the spread of unmanaged OAuth clients. For an evaluation, we recommend asking how client identification fits the team's existing authorization process. Treat that as a design question, rather than assuming the specification alone answers every operational concern.
The update also described an extension mechanism. Enterprise-Managed Authorization grew from Cross App Access. It lets a company identity provider decide which MCP servers an agent may use for a user. The MCP blog names Anthropic, Microsoft and Okta as adopters. That attribution matters: the adoption statement comes from the protocol's blog, not an independent assessment of each implementation.
Our recommendation is to distinguish the core specification from its extensions when reading product claims. Ask which specific mechanism a product documents. A reference to MCP should prompt a more precise question about routing, client metadata or company authorization. This is an editorial test for clarity, not an additional requirement stated by the specification.
For readers using the key, the update supports two routes: gateway policy for each MCP call and delegated access with Cross App Access. The first concerns the gateway's role in the call path. The second concerns access delegated through the company identity provider. We recommend choosing between those needs before comparing products, while allowing for an evaluation that needs both.
A practical review should follow one intended agent task through the proposed arrangement. Ask where the user is represented, where the client identifies itself and where the access decision belongs. These are suggested review questions, not claims about additional protocol features. They help keep the discussion attached to the changes already described.
The editorial takeaway is to avoid treating this release as one undifferentiated identity feature. Read the specification update for the core changes and the authorization post for the extension. Then compare the documented mechanism with the specific result required by the team.
Sources: MCP specification update, 28 July 2026; MCP Enterprise-Managed Authorization, read 2026-11-03