Xage · OAuth Scopes

Xage OAuth Scopes

OAuth 2.0 probed

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

CompanySecurityCybersecurityZero TrustIdentity and Access ManagementPrivileged Access ManagementOperational TechnologyCritical InfrastructureIndustrialAgent Security

Scopes: 0 Flows: Method: probed

Scopes (0)

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

The only OAuth scope Xage publishes anywhere is the single `mcp` scope advertised in the RFC 8414 authorization server metadata and echoed in the RFC 9728 protected resource metadata for the WordPress MCP server on xage.com. No scope or permission reference exists for the Xage Fabric Platform product API — that documentation is customer-only. Nothing here was derived from a spec; there is no published OpenAPI.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-04'
method: probed
source: https://xage.com/.well-known/oauth-authorization-server
note: >-
  The only OAuth scope Xage publishes anywhere is the single `mcp` scope advertised in the RFC 8414
  authorization server metadata and echoed in the RFC 9728 protected resource metadata for the
  WordPress MCP server on xage.com. No scope or permission reference exists for the Xage Fabric
  Platform product API — that documentation is customer-only. Nothing here was derived from a spec;
  there is no published OpenAPI.
authorization_server: https://xage.com
scopes:
- name: mcp
  description: >-
    Access the Model Context Protocol server at https://xage.com/wp-json/mcp/mcp-oauth-server.
    Advertised verbatim as the sole entry in scopes_supported; no finer-grained description is
    published, and no per-tool scopes are declared.
  resource: https://xage.com/wp-json/mcp/mcp-oauth-server
  evidence: https://xage.com/.well-known/oauth-authorization-server
scope_count: 1
docs: null
docs_note: No published scopes or permissions reference page.

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