# Check MCP authorization discovery online

> Free MCP authorization checker: fetch protected resource metadata (RFC 9728) and AS metadata, then check PKCE S256, CIMD, DCR, iss and scopes in your browser.

- URL: https://iamops.dev/tools/mcp-auth/
- Markdown: https://iamops.dev/tools/mcp-auth.md
- Language: en
- Runs in your browser, nothing is uploaded.

Type the URL of an MCP server. I follow the discovery steps of the MCP spec from your browser and check what a client will find there.

## What can I paste here

The MCP server URL, or the Protected Resource Metadata and authorization server metadata JSON if CORS blocks the fetch.

## What it does

- Probes the MCP endpoint, reads the resource_metadata hint from WWW-Authenticate or tries the RFC 9728 well-known URLs in spec order.
- Fetches the authorization server metadata (RFC 8414, then OpenID Connect) and checks the issuer, PKCE S256, CIMD or DCR, RFC 9207 iss and scopes.
- When CORS blocks a call it says so and gives the curl commands, and you can paste the JSON instead.

## Example use

Enter a public MCP server URL, fetch its metadata, and see whether PKCE S256 and a resource indicator are advertised.

## How to read the result

- A 401 with WWW-Authenticate: Bearer resource_metadata=... is what the spec wants. Without the hint, clients try the path-specific well-known URL and then the root.
- The resource in the metadata must be the MCP server URL. A client must not use metadata that names another resource.
- No code_challenge_methods_supported means a client must stop. S256 has to be listed.
- From 2026-07-28, CIMD is the way for a client with no prior relationship to register. DCR still works but is deprecated.

## What it does not do

- Browsers enforce CORS. Many servers do not send CORS headers or hide WWW-Authenticate, so some steps need curl and a paste.
- It does not run an authorization flow, so it cannot prove the AS honours the resource parameter (RFC 8707) or returns iss.
- It follows MCP 2026-07-28. Older servers may follow 2025-11-25 or 2025-06-18, where some rules differ.

## Questions people ask

### What can I paste here

The MCP server URL, or the Protected Resource Metadata and authorization server metadata JSON if CORS blocks the fetch.

### Why does my MCP server fail the discovery check?

Most often the server answers 401 without a resource_metadata hint and has no metadata at /.well-known/oauth-protected-resource, or the resource value differs from the URL clients use.

### Why does the browser say the call was blocked?

The server did not allow cross-origin reads. A desktop MCP client does not care about CORS, so this is not a bug in the server. Run the curl commands and paste the JSON.

## Related

- [Certificate decoder](https://iamops.dev/tools/certificate-decoder.md): Decode an X.509 certificate, chain or CSR and read SANs, expiry, key size, fingerprints and chain order. Paste PEM, base64 DER or hex. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/certificate-decoder/)
- [SAML decoder and verifier](https://iamops.dev/tools/saml.md): Decode a SAMLRequest or SAMLResponse, check the XML signature and decrypt an EncryptedAssertion. Paste base64, raw XML or a redirect URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/saml/)
- [JWT decoder and verifier](https://iamops.dev/tools/jwt.md): Decode a JSON Web Token, show claims and expiry as dates, and verify the signature. Paste a compact JWT, then an HMAC secret, PEM key, JWK or JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/jwt/)
- [ID-JAG inspector](https://iamops.dev/tools/id-jag.md): Inspect an Identity Assertion JWT Authorization Grant against the IETF draft and get the curl requests. Paste a compact ID-JAG token. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/id-jag/)
- [DPoP proof builder and checker](https://iamops.dev/tools/dpop.md): Build a DPoP proof with a fresh ES256 key, or check typ, htm, htu, iat, ath, nonce and the cnf.jkt thumbprint. Paste a DPoP JWT and the method and URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/dpop/)
- [PKCE generator](https://iamops.dev/tools/pkce.md): Generate a PKCE code verifier and S256 challenge, or check that a pair matches, with authorize and token snippets. Paste a verifier and optional challenge, or generate them here. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/pkce/)
- [OIDC discovery and JWKS viewer](https://iamops.dev/tools/oidc-discovery.md): Read an OpenID Provider discovery document and JWKS, and flag missing PKCE, weak keys or risky grants. Type the issuer, or paste the JSON if CORS blocks the fetch. Runs in your browser. Nothing is uploaded to this site; the fetch goes from your browser to the issuer. (https://iamops.dev/tools/oidc-discovery/)
- [Encoder and decoder](https://iamops.dev/tools/encoder-decoder.md): Encode or decode Base64, URL, hex, HTML entities, Unicode, gzip, deflate and the SAML redirect chain, with auto-detect. Paste the text. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/encoder-decoder/)
- [HAR inspector](https://iamops.dev/tools/har-inspector.md): Inspect a HAR file: filter requests, follow the OAuth or SAML flow, decode JWTs, and copy as curl with secrets redacted. Drop a HAR export from DevTools. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/har-inspector/)
- [HTTP client](https://iamops.dev/tools/http-client.md): Call an API from your browser with Basic, Bearer, an API key, or OAuth 2.0 (client credentials, authorization code with PKCE, device code, refresh, token exchange) and optional DPoP. Enter the URL and auth details, or paste a curl command, HAR or OpenAPI definition. The request goes from your browser, not through this site. If CORS blocks the call, the page offers curl instead. (https://iamops.dev/tools/http-client/)
- [SD-JWT and VC decoder](https://iamops.dev/tools/sd-jwt.md): Decode an SD-JWT or SD-JWT VC: split disclosures, recompute digests against _sd, and check the Key Binding JWT. Paste the compact string with ~ separators, and optionally the issuer JWK. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/sd-jwt/)
- [Passkey and WebAuthn decoder](https://iamops.dev/tools/webauthn.md): Decode a WebAuthn or passkey response: attestationObject, clientDataJSON and authenticator data, including flags, AAGUID, sign count and the COSE public key. Paste the credential JSON or the individual fields. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/webauthn/)
- [Shared Signals SET decoder](https://iamops.dev/tools/shared-signals.md): Decode a Shared Signals Security Event Token (CAEP or RISC), explain the event type and the sub_id formats, and optionally verify the signature. Paste the SET JWT and optionally the transmitter JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/shared-signals/)
