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

Protected resource metadata and discovery

MCP servers publish protected resource metadata so clients can find the right authorization server and the scopes on offer. Authorization servers publish their own metadata, and the 2026 spec requires clients to validate the issuer returned in authorization responses. Reading these documents during a review shows exactly what a server will accept.

Read in this order

  1. OfficialRFC 9728: OAuth 2.0 Protected Resource MetadataStart here: the standard a server uses to say which authorization server it trusts.
  2. OfficialRFC 8414: OAuth 2.0 Authorization Server MetadataThe metadata document you fetch to learn endpoints and supported features.
  3. OfficialMCP specification 2026-07-28: Key changesWhat changed in the 2026 spec, including issuer validation.

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.