SimSpace · OAuth Scopes

SimSpace OAuth Scopes

OAuth 2.0 probed

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

CompanyCybersecurityCyber RangeSecurity TrainingSimulationAI AgentsSecurity OperationsCritical InfrastructureGovernmentCompliance
Scopes: 0 Flows: Method: probed

Scopes (0)

SimSpace 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 surface SimSpace publishes anonymously is the one declared in its RFC 8414 authorization-server metadata and echoed in its RFC 9728 protected-resource metadata. It carries a single scope. SimSpace publishes no scopes or permissions reference page for the platform API; if the platform API uses scopes, they are documented only inside the authenticated portal.

📄 Provider scope reference:

Source

OAuth Scopes

simspace-scopes.yml Raw ↑ 
generated: '2026-08-27'
method: probed
source: https://simspace.com/.well-known/oauth-authorization-server
docs: null
note: >-
  The only OAuth scope surface SimSpace publishes anonymously is the one declared in
  its RFC 8414 authorization-server metadata and echoed in its RFC 9728
  protected-resource metadata. It carries a single scope. SimSpace publishes no scopes
  or permissions reference page for the platform API; if the platform API uses scopes,
  they are documented only inside the authenticated portal.
schemes:
- name: oauth2-mcp
  source: https://simspace.com/.well-known/oauth-authorization-server
  authorization_url: https://simspace.com/oauth/authorize
  token_url: https://simspace.com/oauth/token
scopes:
- name: mcp
  description: Access the MCP server surface at https://simspace.com/wp-json/mcp/mcp-oauth-server
  source: scopes_supported in RFC 8414 authorization-server metadata and RFC 9728
    protected-resource metadata
  applies_to: https://simspace.com/wp-json/mcp/mcp-oauth-server
scope_count: 1

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