Discover this authorization server's OAuth 2.1 capabilities
GET
/.well-known/oauth-authorization-server
const url = 'https://api.adversarial.com/api/.well-known/oauth-authorization-server';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.adversarial.com/api/.well-known/oauth-authorization-serverReturns the RFC 8414 authorization server metadata document: the issuer, the authorize/token/registration/revocation endpoint URLs, and the grant types, scopes, client authentication methods, and PKCE challenge methods this server supports. Clients fetch this first to configure themselves instead of hard-coding endpoint URLs.
Responses
Section titled “Responses”Authorization server metadata
Media typeapplication/json
object
authorization_endpoint
required
string
code_challenge_methods_supported
required
Array<string>
grant_types_supported
required
Array<string>
issuer
required
Issuer identifier — also the origin from which the well-known path is
served. MCP clients may use this as the OAuth iss claim expectation.
string
registration_endpoint
required
string
response_types_supported
required
Array<string>
revocation_endpoint
required
string
scopes_supported
required
Array<string>
token_endpoint
required
string
token_endpoint_auth_methods_supported
required
Array<string>
Examplegenerated
{ "authorization_endpoint": "example", "code_challenge_methods_supported": [ "example" ], "grant_types_supported": [ "example" ], "issuer": "example", "registration_endpoint": "example", "response_types_supported": [ "example" ], "revocation_endpoint": "example", "scopes_supported": [ "example" ], "token_endpoint": "example", "token_endpoint_auth_methods_supported": [ "example" ]}