By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Metadata discovery and client registration

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

  1. OfficialRFC 9728: OAuth 2.0 Protected Resource MetadataStart here: how a resource server tells clients which authorization server to use.
  2. OfficialRFC 8414: OAuth 2.0 Authorization Server MetadataThe authorization server metadata format that clients fetch to find endpoints.
  3. OfficialOAuth Client ID Metadata Document (IETF draft)A newer way to identify clients by URL, with less open registration.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.