Cross-check an MCP OAuth deployment
This utility compares resource-server and authorization-server metadata so obvious issuer and discovery mismatches can be found before an OAuth flow is attempted.
Compare protected-resource metadata with authorization-server metadata and detect issuer or configuration mismatches.
This utility compares resource-server and authorization-server metadata so obvious issuer and discovery mismatches can be found before an OAuth flow is attempted.
Cross-check MCP protected resource metadata, authorization server metadata and expected OAuth issuer.
Use MCP Authorization Config Checker as a focused pre-flight utility while building, reviewing or debugging an MCP integration. Paste the relevant configuration, protocol message, metadata, schema or value into the tool and review the returned findings before the same data reaches a production client or server.
Authorization metadata must be treated as security-sensitive configuration. Static validation can reveal obvious inconsistencies, but a production OAuth deployment must also validate live issuer, redirect, token and authorization behavior at runtime.
A clean result means the input passed the rules implemented by this utility. It does not guarantee application security, protocol interoperability or correct business behavior. Test important integrations against the exact MCP client, SDK, gateway and server versions used in your deployment.