O Auth

RFC 7591 Dynamic Client Registration for MCP OAuth clients. Public and unauthenticated, but rate-limited: a redirect URI must be on an allowed first-party origin, and the registered client is public (no secret, token_endpoint_auth_method: none) and constrained to the mcp:use scope. It is redeemed with PKCE at the token endpoint, or through the agent claim ceremony (/oauth/agent/identity + grant_type=claim): the returned grant_types list both authorization_code and the device authorization grant that backs the claim.

OAuth 2.1 token endpoint. Exchanges an authorization code (with PKCE) or a refresh token for a bearer access token. Public — a dynamically registered client is authenticated by its PKCE code_verifier, not a secret.

RFC 7009 token revocation. Revokes the supplied token and the rest of its grant: an access token takes its refresh token with it, and a refresh token takes the access token it belongs to. Public — a client registered without a secret is identified by client_id.

A token that is unknown, malformed, expired, already revoked, or issued to a different client is answered 200 without any change, exactly as RFC 7009 §2.2 requires, so the endpoint never reveals whether a token exists.

The identity_endpoint of the auth.md agent_auth block. An agent that holds a registered client starts a claim here and receives a claim_token and a short user_code. It shows the code to the account owner, who signs in at verification_uri and approves or denies it; meanwhile the agent polls the token endpoint with grant_type=claim. This is the OAuth 2.0 device authorization grant (RFC 8628) under the auth.md request and response names: claim_token is the device code. Public, unauthenticated and rate-limited. No account is created: only an existing, signed-in account can approve.

The events_endpoint of the auth.md agent_auth block. This server issues no identity assertions, so the one event it accepts concerns a token it issued: a token-revoked event revokes that access or refresh token, exactly as POST /oauth/revoke would. The answer is the same whether or not the token existed, so the endpoint reveals nothing about it.

Public discovery document describing the OAuth authorization server.

Public discovery document describing this protected resource and its authorization servers.