Description
An optional, OAuth server configuration could help here as well specifically for those MCP authorizations servers that do not support Dynamic Client Registration.
Described in the spec, Clients could hardcode the ClientId for the authorization server.
The metadata in the registry can help guide consumers a ClientId is expected for the specific MCP server as well as where to acquire it, usually link to service provider developer portals.
For reference see issue - microsoft/vscode#247759 and also briefly touched on DCR topic and clientId acquisition in the blog
The shape of this could be inspired from OAS and/or PRM
Created for tracking from PR comment - https://github.com/modelcontextprotocol/registry/pull/3/files/e9ad7352dd35f905e6216b94cf760d6bd124d8a0#r2077901936