generated: '2026-07-18'
method: searched
source: https://mcp.corvera.ai/.well-known/oauth-authorization-server
docs: https://docs.corvera.ai/quickstart
schemes:
  - name: OAuth2
    source: https://mcp.corvera.ai/.well-known/oauth-authorization-server
    flows:
      - flow: authorizationCode
        authorizationUrl: https://mcp.corvera.ai/authorize
        tokenUrl: https://mcp.corvera.ai/token
        registrationUrl: https://mcp.corvera.ai/register
        pkce: S256
        grant_types: [authorization_code, refresh_token]
        token_endpoint_auth_methods: [client_secret_post, client_secret_basic]
scopes:
  - scope: openid
    description: OpenID Connect authentication (subject identity).
    flows: [authorizationCode]
    sources: [well-known/corvera-oauth-authorization-server.json]
  - scope: email
    description: Access the authenticated user's email address.
    flows: [authorizationCode]
    sources: [well-known/corvera-oauth-authorization-server.json]
  - scope: profile
    description: Access the authenticated user's basic profile.
    flows: [authorizationCode]
    sources: [well-known/corvera-oauth-authorization-server.json]
  - scope: user:org:read
    description: >-
      Read access to the user's organization / workspace context. Combined with
      Corvera's per-account integration gating, this determines which dataset
      tools the connected AI tool can call.
    flows: [authorizationCode]
    sources: [well-known/corvera-oauth-authorization-server.json]
notes: >-
  Scopes are advertised via RFC 8414 metadata on the product MCP server.
  Data-access authorization beyond these OAuth scopes is enforced by Corvera's
  role-based dataset access controls and per-account integration gating rather
  than by additional OAuth scopes.