Get authorization server metadata
/.well-known/oauth-authorization-serverDescribes Chartnaut's OAuth 2.1 authorization server (RFC 8414): the addresses of its endpoints and what it supports. An MCP client reads it once, then registers, authorizes and gets tokens from the addresses it lists.
Scope | Heavy call | Long poll | CLI |
|---|---|---|---|
None, no key | No | No | None |
Guidance
It lives at the root of
https://api.chartnaut.com, not under/v1./.well-known/openid-configurationserves the same document for clients that look there first. Chartnaut is not an OpenID provider and issues no ID tokens.Every client is public: there are no client secrets, and PKCE with
S256is required on every authorization.The only grants are
authorization_codeandrefresh_token. There is no client credentials grant; for a program with no person present, use an API key.Redirects carry
iss, so a client can check the answer came fromhttps://api.chartnaut.com.It is public and cached for 5 minutes.
Response
200 with:
Field | Type | Description |
|---|---|---|
| string |
|
| string | |
| string | |
| string | |
| string | |
| array of string |
|
| array of string |
|
| array of string |
|
| array of string |
|
| array of string |
|
| array of string |
|
| array of string |
|
| boolean |
|
Status codes
Status | Code | Meaning |
|---|---|---|
| - | The metadata |
