Conformance Runner Suites

Connected Apps Reference Consumer & Conformance Inspector

Welcome to the Connected Apps Reference Consumer & Conformance Inspector (@connected-consumer). This application validates any partner Model Context Protocol (MCP) and OAuth 2.1 server (@connected-producer) strictly through a client generated from openapi/producer-openapi.json.

[!IMPORTANT] OpenAPI-Only Wire Contract: Every HTTP request and JSON-RPC 2.0 payload exchanged between this Consumer and a target Producer is driven by openapi/producer-openapi.json and openapi/consumer-openapi.json. If an endpoint, header, or schema property is not declared in the OpenAPI specification, it cannot be invoked.


Consumer Endpoints & OpenAPI Contract

1. Inspect Consumer OpenAPI 3.0.3 Specification

Fetch the Consumer's self-describing OpenAPI 3.0.3 contract (GET /openapi.json / operationId: getConsumerOpenApiSpec) defining the callback, Client ID Metadata Document (CIMD), JWKS, and Conformance Runner endpoints.

2. Inspect IETF Client ID Metadata Document (CIMD)

Fetch GET /.well-known/oauth-client.json (operationId: getClientMetadataDocument). During Use Case 2B, the Consumer passes this URL as its client_id, and the Producer fetches this document using a client generated from consumer-openapi.yaml.

3. Inspect Consumer Public JWKS (RFC 7517)

Fetch GET /.well-known/jwks.json (operationId: getConsumerJwks). The Producer uses this public key set to verify the Consumer's private_key_jwt (RS256) assertions on POST /oauth/token.