{"version":"2.1.248","anchor":"oauth-discovery-schema-accepts-client-id-metadata-documents","canonical_anchor":"oauth-discovery-schema-accepts-client-id-metadata-documents","heading":"OAuth discovery schema accepts client-ID metadata documents","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/oauth-discovery-schema-accepts-client-id-metadata-documents","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### OAuth discovery schema accepts client-ID metadata documents\n\nMCP OAuth discovery now accepts providers advertising client-ID metadata documents.\n\n**What**\n\nThe schema for an OpenID provider's discovery document is now written out in full and accepts an optional `client_id_metadata_document_supported` boolean, which matters for MCP servers authenticating over OAuth.\n\n**Details**\n\n- Required fields are `response_types_supported`, `subject_types_supported` and `id_token_signing_alg_values_supported`, alongside the issuer, endpoints and the various `*_supported` arrays.\n\n**Evidence**\n\n`client_id_metadata_document_supported`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}