CloudHealth · OAuth Scopes

CloudHealth OAuth Scopes

OAuth 2.0 probed

CloudHealth publishes 4 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the CloudHealth API on a user’s behalf.

Tokens are issued from https://apps.cloudhealthtech.com/oauth2/token.

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.

Cloud CostCloud GovernanceCloud ManagementCost OptimizationFinOpsMulti-Cloud

Scopes: 4 Flows: authorizationCode, clientCredentials Method: probed

OAuth endpoints

Authorization URL
https://apps.cloudhealthtech.com/oauth2/authorize

Token URL
https://apps.cloudhealthtech.com/oauth2/token

Flows
authorizationCodeclientCredentials

Scopes (4)

Scope	Description	Flows
mcp:datasets:read		authorizationCode, clientCredentials
mcp:query:run		authorizationCode, clientCredentials
mcp:flexorgs:read		authorizationCode, clientCredentials
mcp:customers:read		authorizationCode, clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-16'
method: probed
source: https://apps.cloudhealthtech.com/.well-known/oauth-authorization-server
note: No OAuth scheme is declared in the (API Evangelist-authored) OpenAPI and the docs publish no scope reference
  page; these scopes are read verbatim from the authorization server's RFC 8414 metadata (scopes_supported), which
  protects the MCP server at https://apps.cloudhealthtech.com/mcp. Descriptions are not published by the provider.
docs: null
schemes:
  - name: CloudHealthOAuth
    source: well-known/cloudhealth-oauth-authorization-server.json
    protects: https://apps.cloudhealthtech.com/mcp
    flows:
      - flow: authorizationCode
        authorizationUrl: https://apps.cloudhealthtech.com/oauth2/authorize
        tokenUrl: https://apps.cloudhealthtech.com/oauth2/token
        pkce: S256
      - flow: clientCredentials
        tokenUrl: https://apps.cloudhealthtech.com/oauth2/token
scopes:
  - scope: mcp:datasets:read
    description: null
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/cloudhealth-oauth-authorization-server.json]
  - scope: mcp:query:run
    description: null
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/cloudhealth-oauth-authorization-server.json]
  - scope: mcp:flexorgs:read
    description: null
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/cloudhealth-oauth-authorization-server.json]
  - scope: mcp:customers:read
    description: null
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/cloudhealth-oauth-authorization-server.json]

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/cloudhealth-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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