SnowSignals · OAuth Scopes

SnowSignals OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://snowsignals.io/v1/oauth/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.

CryptocurrencyMarket DataBitcoinAnalyticsmarket-phaseregimetrendvaneDaaSMCPAgent-NativeFinancial Datax402

Scopes: 1 Flows: Method: probed

OAuth endpoints

Authorization URL
https://snowsignals.io/oauth/authorize

Token URL
https://snowsignals.io/v1/oauth/token

Flows

Scopes (1)

Scope	Description	Flows
daas:read	Read access to the metered/account MCP tools: get_phase, compose_phases (metered) and get_notifications, get_balance, get_usage, deposit_poll (free but account-bound). The two discovery tools (list_phase_meta, phase_resolution_stats) need no scope and no account.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-10'
method: probed
source: >-
  https://snowsignals.io/.well-known/oauth-authorization-server (RFC 8414, fetched 2026-09-10) and
  https://snowsignals.io/.well-known/oauth-protected-resource (RFC 9728); per-tool auth requirements
  read from the live MCP tools/list (mcp/snowsignals-mcp-tools-list.json).
note: >-
  The REST OpenAPI declares only apiKey schemes (url / nonce methods), so OAuth scopes are not in the
  spec — the OAuth surface belongs to the MCP endpoint. One scope exists. Public client with PKCE
  S256, dynamic client registration open at /v1/oauth/register, token endpoint auth method `none`.
authorization_server: https://snowsignals.io
authorization_endpoint: https://snowsignals.io/oauth/authorize
token_endpoint: https://snowsignals.io/v1/oauth/token
registration_endpoint: https://snowsignals.io/v1/oauth/register
protected_resource: https://snowsignals.io/mcp
scopes:
- scope: daas:read
  description: >-
    Read access to the metered/account MCP tools: get_phase, compose_phases (metered) and
    get_notifications, get_balance, get_usage, deposit_poll (free but account-bound). The two
    discovery tools (list_phase_meta, phase_resolution_stats) need no scope and no account.
  operations:
  - get_phase
  - compose_phases
  - get_notifications
  - get_balance
  - get_usage
  - deposit_poll
scope_count: 1

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/snowsignals-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.