Wayground · OAuth Scopes
Wayground OAuth Scopes
OAuth 2.0
probed
Wayground 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.
CompanyEducationEdTechK-12LearningAssessmentArtificial IntelligenceMCPLTIRosteringSingle Sign-On
Scopes: 0
Flows:
Method: probed
Scopes (0)
Wayground 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.
A single all-or-nothing scope is the finding. An agent authorising against Wayground's MCP server cannot request less than everything the scope covers, and cannot tell from any published source what "everything" is.
A single all-or-nothing scope is the finding. An agent authorising against Wayground's MCP server cannot request less than everything the scope covers, and cannot tell from any published source what "everything" is.
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.