@mcp-z/client
    Preparing search index...

    Interface AuthCapabilities

    OAuth server capabilities discovered from .well-known endpoint

    interface AuthCapabilities {
        authorizationEndpoint?: string;
        authorizationResponseIssSupported?: boolean;
        introspectionEndpoint?: string;
        issuer?: string;
        registrationEndpoint?: string;
        resource?: string;
        scopes?: string[];
        supportsDcr: boolean;
        tokenEndpoint?: string;
    }
    Index
    authorizationEndpoint? authorizationResponseIssSupported? introspectionEndpoint? issuer? registrationEndpoint? resource? scopes? supportsDcr tokenEndpoint?
    authorizationEndpoint?: string

    OAuth authorization endpoint

    authorizationResponseIssSupported?: boolean

    Whether the authorization response carries an iss parameter (RFC 9207)

    introspectionEndpoint?: string

    Token introspection endpoint

    issuer?: string

    Issuer identifier from the authorization server metadata (RFC 8414)

    registrationEndpoint?: string

    DCR client registration endpoint

    resource?: string

    The protected resource's canonical identifier, from the RFC 9728 metadata document's resource field. This is what an RFC 8707 resource indicator must carry, and it is the resource server's own statement of its identity - not the URL we happened to dial, and never the base URL discovery was performed against, which has any /mcp segment stripped off it.

    Absent when no protected-resource metadata was published and the authorization server was reached by direct RFC 8414 discovery instead.

    scopes?: string[]

    Supported OAuth scopes

    supportsDcr: boolean

    Whether the server supports Dynamic Client Registration (RFC 7591)

    tokenEndpoint?: string

    OAuth token endpoint

    Settings
    Member Visibility

    On This Page
    Properties