Docs
Discovery

Get where to sign in to the MCP server

GET
/.well-known/oauth-protected-resource/mcp

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.

Header Parameters

X-Correlation-ID?string

An 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.

Match^[A-Za-z0-9._:-]+$
Length1 <= length <= 128

Response Body

The MCP server's protected resource metadata.

application/json
  1. 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*string

The resource identifier, which a token for it names in its audience (RFC 8707).

Formaturi
authorization_servers*array<>

The issuers whose tokens the resource accepts. Each publishes its own metadata (RFC 8414).

Items1 <= items
bearer_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?string

A name for people.

Example Request
curl -X GET 'https://api.cloud.confidential.ai/.well-known/oauth-protected-resource/mcp' \  -H 'X-Correlation-ID: rollout-2026-10-22'
Example Response
{  "resource": "https://api.cloud.confidential.ai/mcp",  "authorization_servers": [    "https://auth.confidential.ai"  ],  "bearer_methods_supported": [    "header"  ],  "resource_name": "Confidential Cloud MCP server"}