Corvera · OAuth Scopes

Corvera OAuth Scopes

OAuth 2.0 searched

Corvera publishes 4 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Corvera API on a user’s behalf.

Tokens are issued from https://mcp.corvera.ai/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyMCPModel Context ProtocolCPGConsumer Packaged GoodsRetailDataContext LayerAI AgentsAnalyticsY Combinator
Scopes: 4 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://mcp.corvera.ai/authorize
Token URL
https://mcp.corvera.ai/token
Flows
authorizationCode

Scopes (4)

ScopeDescriptionFlows
openid OpenID Connect authentication (subject identity). authorizationCode
email Access the authenticated user's email address. authorizationCode
profile Access the authenticated user's basic profile. authorizationCode
user:org:read 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. authorizationCode

Source

OAuth Scopes

corvera-scopes.yml Raw ↑
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.