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.
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.
📄 Provider scope reference: https://www.nextw.com/docs/mcpserver
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.