Unified · OAuth Scopes

Unified OAuth Scopes

OAuth 2.0 probed

Unified uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyAdvertisingSocial MediaDigital AdvertisingMarketingAnalyticsMediaAgentsMCP
Scopes: 0 Flows: Method: probed

Scopes (0)

Unified implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Unified's authorization server advertises exactly one scope. Both the RFC 8414 authorization server metadata and the RFC 9728 protected-resource descriptor for the MCP endpoint list scopes_supported as ["openid"] and nothing else. There is no anonymous permissions or scope reference page to enrich from — docs.unified.com is behind SSO — so this is the complete published scope surface, not a partial read. Fine-grained authorization, if any, is expressed inside the customer's Unified connection rather than in OAuth scope strings.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-02'
method: probed
source: >-
  https://mcp.unified.com/.well-known/oauth-authorization-server (scopes_supported) and
  https://mcp.unified.com/.well-known/oauth-protected-resource/mcp (scopes_supported).
  Probed 2026-09-02.
note: >-
  Unified's authorization server advertises exactly one scope. Both the RFC 8414 authorization
  server metadata and the RFC 9728 protected-resource descriptor for the MCP endpoint list
  scopes_supported as ["openid"] and nothing else. There is no anonymous permissions or scope
  reference page to enrich from — docs.unified.com is behind SSO — so this is the complete
  published scope surface, not a partial read. Fine-grained authorization, if any, is expressed
  inside the customer's Unified connection rather than in OAuth scope strings.
authorization_server: https://mcp.unified.com/
resource: https://mcp.unified.com/mcp
docs: null
scope_count: 1
scopes:
- name: openid
  description: >-
    Advertised verbatim in scopes_supported by both discovery documents. No description is
    published by the provider; the OIDC-standard meaning is assumed by the name only and is not
    asserted here.
  source: https://mcp.unified.com/.well-known/oauth-authorization-server
  required_for:
  - https://mcp.unified.com/mcp

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/unified-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 email required.

GitHub Google LinkedIn

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