Hello Therma · OAuth Scopes

Hello Therma OAuth Scopes

OAuth 2.0 probed

Hello Therma 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.

CompanyInternet of ThingsEnergySustainabilityCold ChainTemperature MonitoringRefrigerationHVACBuilding AutomationFood SafetyFacilities ManagementRestaurantRetailMCPAgents
Scopes: 0 Flows: Method: probed

Scopes (0)

Hello Therma 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: https://www.glaciergrid.com/connector

Source

OAuth Scopes

hello-therma-scopes.yml Raw ↑ 
generated: '2026-08-22'
method: probed
source: https://mcp.glaciergrid.com/.well-known/oauth-authorization-server
docs: https://www.glaciergrid.com/connector
summary: >-
  GlacierGrid's MCP authorization server advertises exactly two scopes. There is no published
  scopes/permissions reference page on the marketing site or the help center, so the
  descriptions below are inferred ONLY from the names plus the access statements GlacierGrid
  publishes on its connector page; they are marked as such and are not vendor copy.
authorization_server: https://mcp.glaciergrid.com/
protected_resources:
- https://mcp.glaciergrid.com/
- https://mcp.glaciergrid.com/mcp
scope_count: 2
scopes:
- name: customer
  description_source: not-published
  inferred_meaning: >-
    Customer-facing access to the authenticated account's own facility data. GlacierGrid
    states "Access is scoped to the locations your account already covers. The connector
    shows you nothing beyond what your GlacierGrid login already grants."
  access: read-only
  evidence: https://www.glaciergrid.com/connector
- name: internal
  description_source: not-published
  inferred_meaning: >-
    Not documented publicly. The name suggests a GlacierGrid-internal audience rather than a
    customer one; no published material describes it.
  access: unknown
  evidence: https://mcp.glaciergrid.com/.well-known/oauth-authorization-server
gaps:
- >-
  No scope reference page exists. A customer or an agent developer cannot learn what
  `internal` grants, nor whether `customer` is required for every tool, without contacting
  support@glaciergrid.com.

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/hello-therma-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.