Skip to main content
GET
Protected-resource metadata
No signed-in session is required. Endpoint-specific tokens, setup secrets or challenges may still be required. Advertises the MCP resource and its authorization server. HTTPS is required outside loopback development. Request conventions · API keys · MCP connections

Response

Successful response. Examples are illustrative; field values vary by record.

resource
string
authorization_servers
string[]
scopes_supported
string[]
bearer_methods_supported
string[]
resource_name
string