iamops.dev
Argo on X RSS feed
ENEnglish

Tools

MCP authorization discovery checker

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.

Your browser calls the server you enter. Nothing goes through this site.

Runs in your browser. Nothing you paste is sent anywhere. Don't paste production private keys.

Run discovery sends plain GET requests from your browser to the MCP URL you typed and to the metadata URLs it finds, with no cookies and no credentials. Nothing goes to iamops.dev and nothing is stored. Anything you paste into the boxes stays on your device.

How to get the input
  1. Call the server without a token. The 401 should carry WWW-Authenticate with resource_metadata:
    curl -i https://mcp.example.com/mcp
  2. Fetch the metadata URL it names, or the URLs in the curl plan this tool prints, and paste the JSON:
    curl -s https://mcp.example.com/.well-known/oauth-protected-resource
  3. The open-source MCP Inspector runs the whole OAuth flow against your server and shows each step:
    npx @modelcontextprotocol/inspector
    MCP Inspector · Docs

Use a test account and throwaway keys. Do not paste production secrets, session cookies or real users' tokens.

What can I paste here#

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

MCP auth discovery checker

Checks follow the authorization part of MCP 2026-07-28.

What the server returned (fill it in by hand if a fetch was blocked)

Paste the WWW-Authenticate value and the JSON from the curl commands. The checks update as you type.

Samples are made with throwaway keys and example.test names. They mean nothing outside this page.

How to read the result#

What it does not do#

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 articles#

The newest posts and labs on the same topic, picked automatically.