Intrinio · OAuth Scopes

Intrinio OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://intrinio-mcp.intrinio.com/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.

FinanceFinancial DataMarket DataStocksOptionsFundamentalsETFsReal-Time Data

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://intrinio-mcp.intrinio.com/authorize

Token URL
https://intrinio-mcp.intrinio.com/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
intrinio	Single advertised scope for the Intrinio MCP server (scopes_supported in the RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata). Grants access to the Intrinio data catalog through the MCP surface; effective dataset entitlements are governed by the account's subscription tier, not by finer-grained OAuth scopes.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-22'
method: searched
source: https://intrinio-mcp.intrinio.com/.well-known/oauth-authorization-server
schemes:
  - name: Intrinio MCP OAuth
    source: well-known/intrinio-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://intrinio-mcp.intrinio.com/authorize
        tokenUrl: https://intrinio-mcp.intrinio.com/token
        refreshUrl: https://intrinio-mcp.intrinio.com/token
    pkce: S256
    dynamic_client_registration: https://intrinio-mcp.intrinio.com/register
    revocation: https://intrinio-mcp.intrinio.com/revoke
scopes:
  - scope: intrinio
    description: >-
      Single advertised scope for the Intrinio MCP server (scopes_supported in the RFC 8414
      authorization-server metadata and RFC 9728 protected-resource metadata). Grants access
      to the Intrinio data catalog through the MCP surface; effective dataset entitlements
      are governed by the account's subscription tier, not by finer-grained OAuth scopes.
    flows: [authorizationCode]
    sources: [well-known/intrinio-oauth-authorization-server.json]
notes: >-
  The core REST API (api-v2.intrinio.com) is API-key authenticated and exposes no OAuth
  scope surface; this scope model applies to the hosted MCP server only.