For AI agents: the documentation index is at /llms.txt, and this page is available as Markdown at /api/auth/oauth-authorization-server-metadata.md.

Authorization server metadata

GET
/.well-known/oauth-authorization-server

RFC 8414 discovery. A remote MCP client fetches this to learn where to register and authorize, having been configured with nothing but the MCP server URL.

issuer must equal the origin this document is served from, which is why it is mounted at the root rather than under /v1/auth. The endpoints it names do sit under that base path; RFC 8414 does not require them to share the issuer's prefix.

Served no-store: a client that cached this across a key or endpoint rotation would fail in a way that looks like our outage.

Response Body

The authorization server's published identity

application/json
  1. response
issuer*string

Equals the origin this document is served from.

Formaturi
authorization_endpoint*string
Formaturi
token_endpoint*string
Formaturi
registration_endpoint*string

Dynamic client registration (RFC 7591).

Formaturi
jwks_uri*string
Formaturi
scopes_supported*array<string>
response_types_supported*array<string>
grant_types_supported*array<string>
code_challenge_methods_supported*array<string>

S256 only; OAuth 2.1 drops "plain".

token_endpoint_auth_methods_supported*array<string>
resources_supported?array<>

RFC 8707 resource identifiers tokens may be minted for.

Example Request
curl -X GET 'https://api.truemarkets.co/.well-known/oauth-authorization-server'
Example Response200
{  "issuer": "http://example.com",  "authorization_endpoint": "http://example.com",  "token_endpoint": "http://example.com",  "registration_endpoint": "http://example.com",  "jwks_uri": "http://example.com",  "scopes_supported": [    "string"  ],  "response_types_supported": [    "string"  ],  "grant_types_supported": [    "string"  ],  "code_challenge_methods_supported": [    "string"  ],  "token_endpoint_auth_methods_supported": [    "string"  ],  "resources_supported": [    "http://example.com"  ]}