Review a Client ID Metadata Document for HTTPS publication, redirect URI structure and common OAuth client metadata problems.
MCP 2026-07-28 prefers Client ID Metadata Documents over Dynamic Client Registration. A stable HTTPS document acts as the client identity metadata source for supporting authorization servers.
Validate MCP Client ID Metadata Documents, redirect URIs and OAuth client metadata.
Use MCP Client Metadata Validator 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.