Tested against fourteen partners. Every result is public.

Between August and November 2026, 11/11 AI took part in the OpenID Foundation AIIM Community Group's MCP Security Interoperability Test as an MCP client, an MCP server, an MCP gateway and an OAuth authorization server. Every test below was run against another organisation's live implementation, logged from our own capture, and filed in the Foundation's public folder where the organiser reviewed it. Nothing on this page is asserted that cannot be read there.

Results are presented at the Gartner Identity & Access Management Summit, Las Vegas, December 7 to 9, 2026.

9 of 9
Every registered role and flow checked
23
Qualifying tests; 25 logs filed
14
Partner organisations, each on its own software
4
Roles: MCP Client, MCP Server, MCP Gateway, OAuth AS

Coverage

As the organiser's dashboard shows it.

Three flows across four roles. A tick means the organiser checked the cell in the Top-level Results Matrix after reviewing both parties' logs. Roles we did not register are marked not registered, not failed.

RoleOAuthCIMDEMA
MCP Client✓✓✓
MCP Server✓not registerednot registered
MCP Gateway✓✓✓
OAuth Authorization Servernot registered✓✓
OpenID Providernot registerednot registerednot registered

OAuth: a client obtains a token from an authorization server and uses an MCP server. CIMD: the client is identified by a metadata document at a URL rather than a registration. EMA: a user's identity is carried from an identity provider into a resource authorization server by an ID-JAG assertion, with three separate organisations in the loop.

The record

Every test we filed.

One authoritative log per run, on the Foundation's templates, in run order. Our logs grade the other parties only; our own role columns are carried by each partner's complementary log in their folder. Every mark cites raw lines from our capture, and every observation states how it is known: observed by us, inferred by us, or stated by partner. Tokens are withheld and replaced by decoded claims.

#LogFlowRun dateOur rolePartner and role
111AIBlockchain-OAuth-WillAdamsOAuth2026-08-10MCP Server and ASWill Adams (independent), MCP Client
211AIBlockchain-OAuth-MeridianVerityOAuth2026-08MCP ClientMeridian Verity, MCP Server
311AIBlockchain-CIMD--Geobeyond-2026-08CIMD2026-08-11, 08-14MCP ClientGeobeyond, OAuth AS
411AIBlockchain-EMA-DescopeEMA2026-08-25MCP Client and Resource ASDescope, OpenID Provider (two-party, kept for the record)
511AIBlockchain-EMA-CKSaaS-DescopeEMA2026-09-03MCP ClientCK SAaS, Resource AS and MCP Server; Descope, OpenID Provider
611AIBlockchain-OAuth--HelisoftOAuth2026-09-24MCP ClientHelisoft, AS (Keycloak) and MCP Server
711AIBlockchain-OAuth--GeobeyondOAuth2026-09-29MCP ClientGeobeyond, AS and MCP Server
811AIBlockchain-CIMD--GeobeyondCIMD2026-09-29MCP ClientGeobeyond, OAuth AS
911AIBlockchain-EMA--LumoinEMA2026-09-30MCP Client and Resource ASLumoin / Verifable, OpenID Provider (two-party, kept for the record)
1011AIBlockchain-OAuth--AuthHubOAuth2026-10-06MCP ClientAuthHub / LogiLoop, AS and MCP Server
1111AIBlockchain-CIMD--AuthHubCIMD2026-10-06MCP ClientAuthHub, OAuth AS
1211AIBlockchain-EMA--HBXLabs-2026-10-06EMA2026-10-06MCP ClientHBX Labs, OpenID Provider, Resource AS and MCP resource
1311AIBlockchain-EMA--CKSAaS-Descope-2026-10-07EMA2026-10-07MCP ClientCK SAaS, Resource AS and MCP Server; Descope, OpenID Provider
1411AIBlockchain-OAuth--AgentCore-2026-10-10OAuth2026-10-10MCP ClientAWS Bedrock AgentCore, AS (Cognito) and MCP Server
1511AIBlockchain-OAuth--Ferentin-2026-10-10OAuth2026-10-10MCP ClientFerentin, AS and MCP Gateway
1611AIBlockchain-EMA--HBXLabs-Descope-2026-10-13EMA2026-10-13MCP ClientDescope, OpenID Provider; HBX Labs, Resource AS and MCP resource
1711AIBlockchain-EMA--Auth0-Lumoin-2026-10-13EMA2026-10-13MCP ClientLumoin, OpenID Provider; Auth0, Resource AS and MCP Server
1811AIBlockchain-EMA--CKSAaS-Curity-2026-10-14EMA2026-10-14Resource AS and MCP ServerCurity, OpenID Provider; CK SAaS, MCP Client
1911AIBlockchain-EMA--HBXLabs-Descope-2026-10-15EMA2026-10-15MCP ClientDescope, OpenID Provider; HBX Labs, Resource AS and MCP resource
2011AIBlockchain-EMA--Auth0-HBXLabs-2026-10-15EMA2026-10-15MCP ClientHBX Labs, OpenID Provider; Auth0, Resource AS and MCP Server
2111AIBlockchain-OAuth--Bravura-2026-10-16OAuth2026-10-16MCP ClientBravura Security, AS and MCP Server
2211AIBlockchain-EMA--Geobeyond-Ferentin-2026-10-16EMA2026-10-16MCP ClientFerentin, OpenID Provider; Geobeyond, Resource AS and MCP Server
2311AIBlockchain-EMA--CKSAaS-AuthHub-2026-10-18EMA2026-10-18Resource AS and MCP ServerAuthHub, OpenID Provider; CK SAaS, MCP Client
2411AIBlockchain-CIMD--CKSAaS-2026-10-26CIMD2026-10-26OAuth ASCK SAaS, MCP Client
2511AIBlockchain-CIMD--Curity-2026-10-27CIMD2026-10-27OAuth ASCurity, MCP Client

Flows: OAuth 8, CIMD 5, EMA 12. Two two-party EMA runs (25 Aug, 30 Sept) are kept for the record and do not count under the organiser's three-party rule.

Tested with

Fourteen organisations, each operating its own implementation.

Listing here records that a test was run and filed. It is not an endorsement by any of them.

AWS Bedrock AgentCore

Authorization server (Cognito) and MCP server

Auth0

Resource authorization server and MCP server

AuthHub / LogiLoop

Authorization server, MCP server, OpenID provider

Bravura Security

Authorization server and MCP server

CK SAaS

MCP client, resource authorization server, MCP server

Curity

MCP client, OpenID provider

Descope

OpenID provider

Ferentin

Authorization server, MCP gateway, OpenID provider

Geobeyond

Authorization server and MCP server

HBX Labs

OpenID provider, resource authorization server, MCP resource

Helisoft

Authorization server (Keycloak) and MCP server

Lumoin / Verifable

OpenID provider

Meridian Verity

MCP server

Will Adams

MCP client (independent participant)

What the tests exercised

Standards underneath, enforcement on top.

OAuth 2.1 with PKCE S256. Client identification by metadata document (CIMD) with private_key_jwt and RS256. Identity assertion authorization grants (ID-JAG) across three organisations. RFC 8414 discovery in all three well-known path forms. RFC 9728 protected-resource metadata. Scope enforced at the resource. Tokens of 300 seconds bound to one audience. Every allowed and denied governed action signed and recorded, verifiable without us.

Evidence discipline: a result appears on this page only if the organiser's matrix shows it or a filed log records it. Where a log relies on a partner's statement, the log says so. Two defects found in our own implementation during partner runs (a sign-in form action and a proxy redirect rewrite, both in October) are recorded in the relevant logs and were fixed inside the test window.