Moz · OAuth Scopes

Moz OAuth Scopes

OAuth 2.0 probed

Moz 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.

SEOSearchMarketingAnalyticsKeywordsBacklinksLocal MarketingDomain AuthorityLink IndexJSON-RPCMCPCompany

Scopes: 0 Flows: Method: probed

Scopes (0)

Moz 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.

📄 Provider scope reference: https://moz.com/api/docs/guides/mcp-servers

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: https://api.moz.com/.well-known/oauth-protected-resource/mcp/v1/data
docs: https://moz.com/api/docs/guides/mcp-servers
summary: >-
  Moz declares a single OAuth scope, "mcp", in both the authorization-server metadata and each MCP
  endpoint's protected-resource metadata. There is no per-resource or per-method scope vocabulary;
  authorization granularity comes from the subscription attached to the account, not from scopes.
authorization_server: https://api.moz.com
applies_to:
- https://api.moz.com/mcp/v1/data
- https://api.moz.com/mcp/v1/local
scope_count: 1
scopes:
- name: mcp
  description: >-
    Access to the Moz MCP surface for the authenticated account. Declared in
    scopes_supported on both /.well-known/oauth-authorization-server and each
    /.well-known/oauth-protected-resource/mcp/v1/* document.
  source: RFC 8414 + RFC 9728 metadata, probed 2026-08-26
notes:
- >-
  The JSON-RPC API at https://api.moz.com/jsonrpc is API-key authenticated and has no scope surface
  at all - see authentication/moz-authentication.yml.
- >-
  Because the beta restricts MCP access to account owners, an MCP token today carries whatever the
  owner's subscription carries; Moz documents no read-only or per-product scope split.

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/moz-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.