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.
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.
| Role | OAuth | CIMD | EMA |
|---|---|---|---|
| MCP Client | ✓ | ✓ | ✓ |
| MCP Server | ✓ | not registered | not registered |
| MCP Gateway | ✓ | ✓ | ✓ |
| OAuth Authorization Server | not registered | ✓ | ✓ |
| OpenID Provider | not registered | not registered | not 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.
| # | Log | Flow | Run date | Our role | Partner and role |
|---|---|---|---|---|---|
| 1 | 11AIBlockchain-OAuth-WillAdams | OAuth | 2026-08-10 | MCP Server and AS | Will Adams (independent), MCP Client |
| 2 | 11AIBlockchain-OAuth-MeridianVerity | OAuth | 2026-08 | MCP Client | Meridian Verity, MCP Server |
| 3 | 11AIBlockchain-CIMD--Geobeyond-2026-08 | CIMD | 2026-08-11, 08-14 | MCP Client | Geobeyond, OAuth AS |
| 4 | 11AIBlockchain-EMA-Descope | EMA | 2026-08-25 | MCP Client and Resource AS | Descope, OpenID Provider (two-party, kept for the record) |
| 5 | 11AIBlockchain-EMA-CKSaaS-Descope | EMA | 2026-09-03 | MCP Client | CK SAaS, Resource AS and MCP Server; Descope, OpenID Provider |
| 6 | 11AIBlockchain-OAuth--Helisoft | OAuth | 2026-09-24 | MCP Client | Helisoft, AS (Keycloak) and MCP Server |
| 7 | 11AIBlockchain-OAuth--Geobeyond | OAuth | 2026-09-29 | MCP Client | Geobeyond, AS and MCP Server |
| 8 | 11AIBlockchain-CIMD--Geobeyond | CIMD | 2026-09-29 | MCP Client | Geobeyond, OAuth AS |
| 9 | 11AIBlockchain-EMA--Lumoin | EMA | 2026-09-30 | MCP Client and Resource AS | Lumoin / Verifable, OpenID Provider (two-party, kept for the record) |
| 10 | 11AIBlockchain-OAuth--AuthHub | OAuth | 2026-10-06 | MCP Client | AuthHub / LogiLoop, AS and MCP Server |
| 11 | 11AIBlockchain-CIMD--AuthHub | CIMD | 2026-10-06 | MCP Client | AuthHub, OAuth AS |
| 12 | 11AIBlockchain-EMA--HBXLabs-2026-10-06 | EMA | 2026-10-06 | MCP Client | HBX Labs, OpenID Provider, Resource AS and MCP resource |
| 13 | 11AIBlockchain-EMA--CKSAaS-Descope-2026-10-07 | EMA | 2026-10-07 | MCP Client | CK SAaS, Resource AS and MCP Server; Descope, OpenID Provider |
| 14 | 11AIBlockchain-OAuth--AgentCore-2026-10-10 | OAuth | 2026-10-10 | MCP Client | AWS Bedrock AgentCore, AS (Cognito) and MCP Server |
| 15 | 11AIBlockchain-OAuth--Ferentin-2026-10-10 | OAuth | 2026-10-10 | MCP Client | Ferentin, AS and MCP Gateway |
| 16 | 11AIBlockchain-EMA--HBXLabs-Descope-2026-10-13 | EMA | 2026-10-13 | MCP Client | Descope, OpenID Provider; HBX Labs, Resource AS and MCP resource |
| 17 | 11AIBlockchain-EMA--Auth0-Lumoin-2026-10-13 | EMA | 2026-10-13 | MCP Client | Lumoin, OpenID Provider; Auth0, Resource AS and MCP Server |
| 18 | 11AIBlockchain-EMA--CKSAaS-Curity-2026-10-14 | EMA | 2026-10-14 | Resource AS and MCP Server | Curity, OpenID Provider; CK SAaS, MCP Client |
| 19 | 11AIBlockchain-EMA--HBXLabs-Descope-2026-10-15 | EMA | 2026-10-15 | MCP Client | Descope, OpenID Provider; HBX Labs, Resource AS and MCP resource |
| 20 | 11AIBlockchain-EMA--Auth0-HBXLabs-2026-10-15 | EMA | 2026-10-15 | MCP Client | HBX Labs, OpenID Provider; Auth0, Resource AS and MCP Server |
| 21 | 11AIBlockchain-OAuth--Bravura-2026-10-16 | OAuth | 2026-10-16 | MCP Client | Bravura Security, AS and MCP Server |
| 22 | 11AIBlockchain-EMA--Geobeyond-Ferentin-2026-10-16 | EMA | 2026-10-16 | MCP Client | Ferentin, OpenID Provider; Geobeyond, Resource AS and MCP Server |
| 23 | 11AIBlockchain-EMA--CKSAaS-AuthHub-2026-10-18 | EMA | 2026-10-18 | Resource AS and MCP Server | AuthHub, OpenID Provider; CK SAaS, MCP Client |
| 24 | 11AIBlockchain-CIMD--CKSAaS-2026-10-26 | CIMD | 2026-10-26 | OAuth AS | CK SAaS, MCP Client |
| 25 | 11AIBlockchain-CIMD--Curity-2026-10-27 | CIMD | 2026-10-27 | OAuth AS | Curity, 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.