Metadata documents let a client discover an authorization server's endpoints and a protected resource's authorization server without manual setup. MCP depends on these discovery and registration standards, and each fetched URL is a place where a malicious server can try SSRF or phishing.
Read in this order
- OfficialRFC 9728: OAuth 2.0 Protected Resource MetadataStart here: how a resource server tells clients which authorization server to use.
- OfficialRFC 8414: OAuth 2.0 Authorization Server MetadataThe authorization server metadata format that clients fetch to find endpoints.
- OfficialOAuth Client ID Metadata Document (IETF draft)A newer way to identify clients by URL, with less open registration.