MCP authorization discovery checker
An MCP client finds how to sign in from three documents: the WWW-Authenticate header of a 401 response, the protected resource metadata (RFC 9728) and the authorization server metadata (RFC 8414). Paste what your server returns and check that they agree. Runs in your browser; we only count anonymous visits.
How to use this tool
- Enter your MCP server URL: the page shows where clients look for the discovery documents.
- Fetch those addresses with your own tools (for example
curl -ion the MCP URL for the 401 header) and paste the results. The page does not fetch anything itself, so there are no browser CORS problems and no URL leaves your device. - Fix the high-severity findings first: they are the ones that make clients fail to sign in.
Example
The pre-filled values are a consistent set for an invented server and show no problems. Change the issuer in the authorization server metadata to another host to see the mismatch finding, or remove code_challenge_methods_supported to see why clients refuse to continue without PKCE.
Limits
The checks follow RFC 9728, RFC 8414, RFC 7591 and the OAuth security guidance in RFC 9700. The MCP authorization specification is revised often (for example how clients identify themselves); compare the result with the revision your clients target. This page cannot prove that your server issues or validates tokens correctly.
Privacy and security of what you enter
Metadata is public by design, but do not paste tokens or secrets. Nothing is uploaded. See the privacy notice.
We review OAuth 2.1 setups for MCP servers. See the MCP security service, the tool definition check or the OAuth2 error doctor.
Message us on LinkedIn