Get where to sign in to the MCP server
Returns the protected resource metadata (RFC 9728) of the MCP server
at https://api.cloud.confidential.ai/mcp, which MCP clients read
before they sign a person in. A token issued for the MCP server
works only there, and one issued for the API only on the API. No
credential needed.
X-Correlation-ID?stringAn id of your own for this request, or for a group of requests, to
find them in our logs and yours. Logged with the request and returned
unchanged in X-Correlation-ID. The request id itself is always the
API's own, in X-Request-ID.
^[A-Za-z0-9._:-]+$1 <= length <= 128The MCP server's protected resource metadata.
application/json- response
OAuth 2.0 protected resource metadata, as RFC 9728 defines it, which
is why its field names are not camelCase. Ignore fields you do not
know. It lists no scopes_supported, because a token's scopes come
from the person's role in the org, not from what the client asks
for.
resource*stringThe resource identifier, which a token for it names in its audience (RFC 8707).
uriauthorization_servers*array<>The issuers whose tokens the resource accepts. Each publishes its own metadata (RFC 8414).
1 <= itemsbearer_methods_supported?array<string>How to send a token: header, as Authorization: Bearer, and
never in a query string. Open set; accept values not listed.
resource_name?stringA name for people.
curl -X GET 'https://api.cloud.confidential.ai/.well-known/oauth-protected-resource/mcp' \ -H 'X-Correlation-ID: rollout-2026-10-22'{ "resource": "https://api.cloud.confidential.ai/mcp", "authorization_servers": [ "https://auth.confidential.ai" ], "bearer_methods_supported": [ "header" ], "resource_name": "Confidential Cloud MCP server"}