MCP OAuth discovery now accepts providers advertising client-ID metadata documents.
What's wrong with this entry?
The 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.
- Required fields are
response_types_supported,subject_types_supportedandid_token_signing_alg_values_supported, alongside the issuer, endpoints and the various*_supportedarrays.
client_id_metadata_document_supported
Strings lifted out of the shipped bundle, so the claim above can be checked against them.