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

MCP authorization

Remote MCP servers that use the spec's authorization protect their tools with OAuth 2.1: the server is a protected resource, advertises its authorization server through protected resource metadata, and accepts only tokens issued for itself. Local stdio servers use other credentials. The 2026-07-28 revision prefers Client ID Metadata Documents and requires issuer validation. Mistakes cause token passthrough and confused deputies.

Read in this order

  1. OfficialUnderstanding Authorization in MCP (tutorial)Start here: a tutorial walking through the MCP authorization flow end to end.
  2. OfficialAuthorization (MCP specification)The normative rules a compliant server and client must follow.
  3. OfficialRFC 9728: OAuth 2.0 Protected Resource MetadataThe standard behind how a server tells clients which authorization server to use.

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.