Hello Therma website screenshot

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 is listed with 1 API on the APIs.io network. Tagged areas include Company, IoT, Energy, Sustainability, and Cold Chain.

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

30.1/100 thin ▬ flat Agent 33/100 agent ready Front door AI 3/6 light saas Full breakdown ↓
scored 2026-10-23 · rubric v0.25.0 · Show this score on your site →
AccessSelf serve
1 API 1 MCP Servers
CompanyIoTEnergySustainabilityCold ChainTemperature MonitoringRefrigerationHVACBuilding AutomationFood SafetyFacilities ManagementRestaurantRetailMCPAgents

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-23 · rubric v0.25.0
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.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
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/.
Show this score on your site. Kin Score badge preview for Hello Therma It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/hello-therma/"><img src="https://apis.io/badge/hello-therma/card.svg" alt="Hello Therma on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. 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. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Building Automation (HVAC, BACnet, KNX, smart buildings) undeclared - - -
Food Safety (GFSI-recognised certification) undeclared - - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

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.

GlacierGrid MCP Server

GlacierGrid (formerly Therma / Hello Therma) operates a first-party remote MCP server that exposes read-only facility monitoring data — HVAC, refrigeration, energy and savings, ...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Hello Therma Rate Limits

1 limits

RATE LIMITS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hello Therma Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hello Therma Scopes

2 scopes

2 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
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-10-06'
tags:
- Company
- IoT
- Energy
- Sustainability
- Cold Chain
- Temperature Monitoring
- Refrigeration
- HVAC
- Building Automation
- Food Safety
- Facilities Management
- Restaurant
- Retail
- MCP
- Agents
tags_raw:
- Company
- Internet of Things
- Energy
- Sustainability
- Cold Chain
- Temperature Monitoring
- Refrigeration
- HVAC
- Building Automation
- Food Safety
- Facilities Management
- Restaurants
- Retail
- Model Context Protocol
- Agents
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Hosts
  url: hosts/hello-therma-hosts.yml
- type: Vendors
  url: vendors/hello-therma-vendors.yml
- type: Newsroom
  url: https://www.glaciergrid.com/company/newsroom
- type: Leadership
  url: https://www.glaciergrid.com/company/leadership
- url: https://www.glaciergrid.com/company/newsroom
  type: Blog
- url: https://www.glaciergrid.com/company/newsroom/rss.xml
  type: BlogRSS
- 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: MCPServer
  url: mcp/hello-therma-mcp.yml
- type: WellKnown
  url: well-known/hello-therma-well-known.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
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:
  - MCP
  - Agents
  - Monitoring
  - Energy
  tags_raw:
  - Model Context Protocol
  - Agents
  - Monitoring
  - Energy
  properties:
  - type: MCPServer
    url: mcp/hello-therma-mcp.yml
  - type: Documentation
    url: https://www.glaciergrid.com/connector
  aid: hello-therma:glaciergrid-mcp-server
x-enrichment:
  date: '2026-10-20'
  status: nochange
  artifacts_added: 0
  pass: local-v5
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: GlacierGrid (formerly Hello Therma) ships no REST/GraphQL contract; its only machine surface, the remote MCP server
    at mcp.glaciergrid.com/mcp, answers 401 with RFC 9728 metadata so tools/list needs a customer OAuth login.
  evidence:
  - url: https://mcp.glaciergrid.com/mcp
    status: 401
  - url: https://mcp.glaciergrid.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://www.glaciergrid.com/connector
    status: 200
  checked: '2026-10-20'

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

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