Nextworld · OAuth Scopes

Nextworld OAuth Scopes

OAuth 2.0 probed

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

CompanyEnterprise Resource PlanningNo-CodeEnterprise Application PlatformWorkflow-AutomationArtificial IntelligenceMCPIntegrationManufacturingDistribution
Scopes: 0 Flows: Method: probed

Scopes (0)

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

These are not derived from an OpenAPI securityScheme — Nextworld publishes no OpenAPI. They are read verbatim from the RFC 9728 protected-resource metadata the MCP endpoint serves anonymously, captured at well-known/nextworld-oauth-protected-resource.json (HTTP 200, 2026-08-26). The authorization server is an AWS Cognito user pool, whose OIDC discovery document advertises only the four standard OIDC scopes; the resource-specific scope is declared by the resource server.

Source

OAuth Scopes

nextworld-scopes.yml Raw ↑
generated: '2026-08-26'
method: probed
source: https://apps.nextworld.net/ai/mcp/.well-known/oauth-protected-resource
docs: https://www.nextw.com/docs/mcpserver
name: Nextworld OAuth scopes
note: >-
  These are not derived from an OpenAPI securityScheme — Nextworld publishes no OpenAPI. They are
  read verbatim from the RFC 9728 protected-resource metadata the MCP endpoint serves anonymously,
  captured at well-known/nextworld-oauth-protected-resource.json (HTTP 200, 2026-08-26). The
  authorization server is an AWS Cognito user pool, whose OIDC discovery document advertises only the
  four standard OIDC scopes; the resource-specific scope is declared by the resource server.
authorization_servers:
- issuer: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_EJas25nD4
  authorization_endpoint: https://464682c0-7c75-11f1-9d48-12d6f76c75f7.auth.us-east-1.amazoncognito.com/oauth2/authorize
  token_endpoint: https://464682c0-7c75-11f1-9d48-12d6f76c75f7.auth.us-east-1.amazoncognito.com/oauth2/token
  revocation_endpoint: https://464682c0-7c75-11f1-9d48-12d6f76c75f7.auth.us-east-1.amazoncognito.com/oauth2/revoke
  userinfo_endpoint: https://464682c0-7c75-11f1-9d48-12d6f76c75f7.auth.us-east-1.amazoncognito.com/oauth2/userInfo
  jwks_uri: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_EJas25nD4/.well-known/jwks.json
protected_resources:
- resource: https://apps.nextworld.net/ai/mcp
  bearer_methods_supported:
  - header
  - body
scope_count: 5
scopes:
- name: https://apps.nextworld.net/ai/mcp/access
  type: resource
  description: >-
    Resource-server scope granting an MCP client access to the Nextworld MCP endpoint. Nextworld
    publishes no separate per-operation scopes — actual authorization is enforced downstream by the
    platform's own RUID permission model (security groups, permission definitions, roles, role
    hierarchies, org unit security), scoped to the connecting user.
- name: openid
  type: oidc
  description: Standard OpenID Connect scope; requests an ID token.
- name: email
  type: oidc
  description: Standard OIDC claim scope; email and email_verified.
- name: phone
  type: oidc
  description: Standard OIDC claim scope; phone_number and phone_number_verified.
- name: profile
  type: oidc
  description: Standard OIDC claim scope; basic profile claims.
gaps:
- >-
  There is no published scope reference page. Nextworld does not document a granular scope surface
  for its REST endpoints; inbound REST calls authenticate with Basic Auth and receive a short-lived
  bearer token rather than a scoped OAuth grant.

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

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