Client ID Metadata Document support #1150
Description
Instead of DCR, newer spec also allows the use of Client ID Metadata Documents: https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#client-id-metadata-documents
It will be nice to support authenticating with servers using that when possible or the server doesn't support DCR.
I think this might require a public client ID metadata document, and hopefully compliant servers allow any port when localhost is specified with "application_type": "native", or otherwise running on the default localhost port, or one served from the MCP inspector itself, and the MCP server being inspected running alongside the MCP inspector so it can access it via localhost.