Hello Therma

Hello Therma is the original brand of Therma, Inc., the San Francisco cold-chain and cooling intelligence company founded in 2014 by Manik Suri, which rebranded as GlacierGrid in February 2024 and now operates as GlacierGrid, Inc. out of Richmond, Virginia. The platform pairs LoRaWAN temperature and humidity sensors, cellular monitoring hubs and BAS integrations with a cloud dashboard that gives multi-unit retail, restaurant, convenience-store, education and fitness operators remote refrigeration and HVAC monitoring, automated temperature logging for HACCP-style food-safety reporting, equipment-failure prediction and energy optimization across 50 to 500 locations. GlacierGrid publishes no REST, GraphQL or SOAP API and no developer portal; its single machine-callable surface is a first-party remote Model Context Protocol server at mcp.glaciergrid.com, marketed as the GlacierGrid Connector for Claude, which exposes read-only facility, sensor, alert and energy data to an agent under OAuth with account-scoped permissions.

Hello Therma publishes 1 API on the APIs.io network. Tagged areas include Company, Internet of Things, Energy, Sustainability, and Cold Chain.

Hello Therma’s developer surface includes documentation, support, engineering blog, signup flow, changelog, authentication, and 19 more developer resources.

🌐 Visit website 📡 Source on GitHub

36.2/100 thin ▬ flat Agent 11/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0

1 APIs 1 MCP Servers

Company Internet of Things Energy Sustainability Cold Chain Temperature Monitoring Refrigeration HVAC Building Automation Food Safety Facilities ManagementRestaurantsRetailModel Context ProtocolAgents

Kin Score

Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0

Composite quality — 36.2/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 4.9 / 17

Operational Transparency 6.1 / 11

Contract Governance 1.9 / 10

Discoverability 7.4 / 9

Regulatory Posture 9.5 / 15

Agent readiness — 11/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Surface 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/hello-therma: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

GlacierGrid MCP Server

First-party remote Model Context Protocol server exposing read-only GlacierGrid facility monitoring data — HVAC, refrigeration, energy and savings, sensor readings, issues, noti...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Rate Limits 1

Documented rate limits and quota policies.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hello Therma Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

WellKnown

WellKnown

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Conformance

Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

Compliance

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

RateLimits

ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: hello-therma
name: Hello Therma
description: Hello Therma is the original brand of Therma, Inc., the San Francisco cold-chain and cooling intelligence company
  founded in 2014 by Manik Suri, which rebranded as GlacierGrid in February 2024 and now operates as GlacierGrid, Inc. out
  of Richmond, Virginia. The platform pairs LoRaWAN temperature and humidity sensors, cellular monitoring hubs and BAS integrations
  with a cloud dashboard that gives multi-unit retail, restaurant, convenience-store, education and fitness operators remote
  refrigeration and HVAC monitoring, automated temperature logging for HACCP-style food-safety reporting, equipment-failure
  prediction and energy optimization across 50 to 500 locations. GlacierGrid publishes no REST, GraphQL or SOAP API and no
  developer portal; its single machine-callable surface is a first-party remote Model Context Protocol server at mcp.glaciergrid.com,
  marketed as the GlacierGrid Connector for Claude, which exposes read-only facility, sensor, alert and energy data to an
  agent under OAuth with account-scoped permissions.
url: https://raw.githubusercontent.com/api-evangelist/hello-therma/refs/heads/main/apis.yml
image: https://www.glaciergrid.com/hubfs/Glacier%20Grid%20Primary%20Teal-2.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-22'
modified: '2026-08-22'
tags:
- Company
- Internet of Things
- Energy
- Sustainability
- Cold Chain
- Temperature Monitoring
- Refrigeration
- HVAC
- Building Automation
- Food Safety
- Facilities Management
- Restaurants
- Retail
- Model Context Protocol
- Agents
apis:
- name: GlacierGrid MCP Server
  description: First-party remote Model Context Protocol server exposing read-only GlacierGrid facility monitoring data —
    HVAC, refrigeration, energy and savings, sensor readings, issues, notifications, device connectivity and site weather
    — to an MCP client. Marketed as the GlacierGrid Connector for Claude and installed from the Claude connector directory.
    OAuth protected with `internal` and `customer` scopes, streamable-HTTP transport, no write operations. tools/list is auth-gated,
    so the tool schemas are not publicly readable.
  humanURL: https://www.glaciergrid.com/connector
  baseURL: https://mcp.glaciergrid.com/mcp
  tags:
  - Model Context Protocol
  - Agents
  - Monitoring
  - Energy
  properties:
  - type: MCPServer
    url: mcp/hello-therma-mcp.yml
  - type: Documentation
    url: https://www.glaciergrid.com/connector
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/hello-therma-domain-security.yml
- type: Website
  url: https://www.glaciergrid.com/
- type: Documentation
  url: https://www.glaciergrid.com/connector
- type: Support
  url: https://www.glaciergrid.com/helpcenter
- type: Blog
  url: https://www.glaciergrid.com/resources/research-and-impact
- type: SignUp
  url: https://dashboard.glaciergrid.com/
- type: TermsOfService
  url: https://www.glaciergrid.com/terms
- type: PrivacyPolicy
  url: https://www.glaciergrid.com/privacy
- type: GitHubOrganization
  url: https://github.com/glaciergrid
- type: StatusPage
  url: https://www.glaciergrid.com/status-page
- type: ChangeLog
  url: https://www.glaciergrid.com/resources/product-features
- type: LLMsTxt
  url: llms/hello-therma-llms.txt
- type: MCPServer
  url: mcp/hello-therma-mcp.yml
- type: WellKnown
  url: well-known/hello-therma-well-known.yml
- type: Authentication
  url: authentication/hello-therma-authentication.yml
- type: OAuthScopes
  url: scopes/hello-therma-scopes.yml
- type: RateLimits
  url: rate-limits/hello-therma-rate-limits.yml
- type: ErrorCatalog
  url: errors/hello-therma-problem-types.yml
- type: Conventions
  url: conventions/hello-therma-conventions.yml
- type: Conformance
  url: conformance/hello-therma-conformance.yml
- type: Compliance
  url: conformance/hello-therma-conformance.yml
- type: Lifecycle
  url: lifecycle/hello-therma-lifecycle.yml
- type: ChangeLog
  url: changelog/hello-therma-changelog.yml
- type: Plans
  url: plans/hello-therma-plans-pricing.yml
- type: Packages
  url: packages/hello-therma-packages.yml
x-enrichment:
  date: '2026-08-22'
  status: enriched
  artifacts_added: 17
  pass: local-v1
x-coverage:
  state: covered
  reason: mcp-only-contract
  detail: Hello Therma trades as GlacierGrid since February 2024; it ships no OpenAPI, GraphQL, gRPC or WSDL contract, but
    it does operate a live first-party remote MCP server at https://mcp.glaciergrid.com/mcp whose tools/list is OAuth-gated
    (401 with RFC 9728 resource_metadata), so the tool schemas require an authenticated customer account.
  evidence:
  - url: https://mcp.glaciergrid.com/mcp
    status: 401
  - url: https://mcp.glaciergrid.com/.well-known/oauth-protected-resource/mcp
    status: 200
  - url: https://www.glaciergrid.com/en/llms.txt
    status: 200
  - url: https://www.hellotherma.com/
    status: 301
  checked: '2026-08-22'

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/hello-therma"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/hello-therma/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/hello-therma/evidence"

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.

Hello Therma

Kin Score

APIs 1

GlacierGrid MCP Server

MCP Servers 1

GlacierGrid MCP Server

Pricing Plans 1

Hello Therma Plans Pricing

Rate Limits 1

Hello Therma Rate Limits

Security Posture 2

Hello Therma Authentication

Hello Therma Domain Security

Scopes 1

Hello Therma Scopes

Resources

Get Started 1

Documentation 1

Agent Surfaces 3

Design & Contract 4

Build 2

Access & Security 4

Operate 5

Commercial 3

Company 2

Source (apis.yml)

Work with this as data

MCP server

Tools for providers

Call it yourself

Get an API key