StorONE · OAuth Scopes

StorONE OAuth Scopes

OAuth 2.0 probed

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

StorageEnterprise StorageSoftware-Defined StorageData ManagementInfrastructureBlock StorageFile StorageObject StorageBackupReplicationSnapshotsCompany

Scopes: 0 Flows: Method: probed

Scopes (0)

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

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-29'
method: probed
source: https://www.storone.com/.well-known/oauth-authorization-server
name: StorONE OAuth scopes
description: >-
  Only one of StorONE's two API surfaces uses OAuth at all. The S1 REST API on a customer's
  controller nodes authenticates with a session token and has no scope model whatsoever — access is
  governed by the S1 user account, not by scopes. The MCP server on www.storone.com publishes an
  RFC 8414 authorization server metadata document declaring exactly one scope.
surfaces:
  - id: mcp-oauth
    authorization_server: https://www.storone.com
    scope_count: 1
    scopes:
      - name: mcp
        description: >-
          The single scope advertised in scopes_supported. StorONE publishes no scope reference page
          and no finer-grained scopes, so what this scope grants inside the MCP server cannot be
          stated from public material — enumerating the tools it covers requires an authenticated
          tools/list call.
        source: https://www.storone.com/.well-known/oauth-authorization-server
  - id: s1-rest-api
    scope_count: 0
    scopes: []
    note: >-
      No oauth2 security scheme and no scope vocabulary in the REST API reference. Authorization is
      the S1 user's own role on the system; object-store access keys carry a separate `role`
      parameter (see POST /applications/objects/access_keys/create) but that is an S3-style object
      permission, not an OAuth scope.
docs: null
docs_note: StorONE publishes no scopes/permissions reference page for either surface.

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