# SuperhotGeo (remote · superhotgeo.com)

Superhot rock geothermal: well registry with failures at temperature, projects, research, RockLab.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `superhotgeo.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-superhotgeo-superhotgeo/superhotgeo.md), [page](https://verifymcp.io/servers/com-superhotgeo-superhotgeo/superhotgeo)

## Channel facts

- Endpoint: `https://superhotgeo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1022 tokens (~146/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SuperhotGeo MCP server?

SuperhotGeo is a hosted endpoint at https://superhotgeo.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-superhotgeo-superhotgeo 'https://superhotgeo.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-superhotgeo-superhotgeo": {
      "url": "https://superhotgeo.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-superhotgeo-superhotgeo": {
      "type": "http",
      "url": "https://superhotgeo.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-superhotgeo-superhotgeo]
url = "https://superhotgeo.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-superhotgeo-superhotgeo": {
      "type": "remote",
      "url": "https://superhotgeo.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-superhotgeo-superhotgeo --url 'https://superhotgeo.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-superhotgeo-superhotgeo:
    url: "https://superhotgeo.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-superhotgeo-superhotgeo": {
      "Transport": "http",
      "Url": "https://superhotgeo.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-superhotgeo-superhotgeo -t streamable-http -u 'https://superhotgeo.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-superhotgeo-superhotgeo": {
      "type": "http",
      "url": "https://superhotgeo.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 66)

First indexed and scored.

## MCP tools (7)

### `search` (~155 tokens)

Search SuperhotGeo

Search SuperhotGeo's curated records — the Superhot Well Registry, projects, field lessons, RockLab models and datasets, open engineering problems, and the research library. Use it first for any question about superhot rock geothermal, supercritical (>374 C) geothermal, enhanced/engineered geothermal systems (EGS), deep or magma-proximal drilling, high-temperature well failures (casing, cement, elastomers, electronics, scaling, induced seismicity), geothermal projects and companies, and firm clean power for AI and data centers. Returns ids to pass to `fetch`.

Input parameters:

- `query` (string, required): Natural-language or keyword query, e.g. "casing failure above 400 C" or "magma Krafla".

### `fetch` (~47 tokens)

Fetch a SuperhotGeo record

Fetch the full text of one record returned by `search`, with its canonical URL and source.

Input parameters:

- `id` (string, required): An id from `search`, formatted "<resource>:<recordId>".

### `search_wells` (~162 tokens)

Search the Superhot Well Registry

Search documented superhot and high-temperature geothermal wells worldwide (IDDP, Venelle-2, Kakkonda, Nesjavellir, The Geysers, Puna, Utah FORGE, Fervo, Mazama and more): max temperature, depth, lithology, what failed at temperature, root cause, lessons, induced seismicity, and a public source per well. Use it for drilling, completion, materials, site-comparison, or risk questions.

Input parameters:

- `minTempC` (number): Only wells at or above this max temperature (°C). 374 = supercritical.
- `query` (string): Optional keywords: a well, country, operator, rock type, or failure mode (e.g. "cement", "seismicity").

### `ask_superhot` (~82 tokens)

Ask the SuperhotGeo Assistant any question about superhot rock / next-generation (supercritical, EGS) geothermal energy — the science, technology, projects, economics, policy, companies, or the SuperhotGeo platform. Returns a grounded answer with cited web sources. Requires a SuperhotGeo API key.

Input parameters:

- `question` (string, required): The question to ask.

### `search_library` (~61 tokens)

Search SuperhotGeo's continuously curated library of superhot geothermal news, studies, journals, and resources.

Input parameters:

- `limit` (integer): Max results (default 25).
- `query` (string, required): Keywords to match against title, description, author, or source.

### `list_resource` (~301 tokens)

List records from a SuperhotGeo public collection. "trending" = the ranked front-page board of what the field is paying attention to right now (recomputed every 6h from recent saves/views + recency), each row carrying its rank, type, refId, and a one-line label; "projects" = superhot/next-gen geothermal projects & regions; "pioneers" = people & orgs; "vendors" = drilling/subsurface marketplace; "testbeds" = shared field labs & open data; "lessons" = hard-won field lessons; "conferences" = geothermal conferences & summits worldwide, kept current; "exchange" = supply/RFQ/group-buy board; "offtake" = power↔demand board; "datasets" = open geothermal datasets; "artifacts" = RockLab models, datasets, and benchmarks with versions, licenses, provenance, metrics, and reproducibility status; "insights" = cross-connections; "problems" = hard open engineering problems the SuperhotGeo Reasoning Engine works on, each with a reasoned answer; "field_data" = the vetted field/well dataset (measured temperatures, depths, lithology, rates, and what failed at superhot conditions).

Input parameters:

- `limit` (integer): Max results (default 25).
- `q` (string): Optional keyword filter.
- `resource` (string, required): Which collection to list.

### `get_resource` (~39 tokens)

Fetch a single SuperhotGeo record by resource and id.

Input parameters:

- `id` (string, required): The record id.
- `resource` (string, required): Which collection.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-superhotgeo-superhotgeo/superhotgeo#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 66
- 2026-10-25: 66

## Common questions

### What is the SuperhotGeo MCP server?

SuperhotGeo is an MCP server listed in the public MCP registry as com.superhotgeo/superhotgeo. Superhot rock geothermal: well registry with failures at temperature, projects, research, RockLab. This page covers its hosted endpoint (https://superhotgeo.com/mcp).

### Is the SuperhotGeo MCP server safe to use?

SuperhotGeo scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SuperhotGeo MCP server expose?

SuperhotGeo exposes 7 tools: search, fetch, search_wells, ask_superhot, search_library, and 2 more. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.

### Does the SuperhotGeo MCP server require authentication?

No. We connected to SuperhotGeo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SuperhotGeo MCP server still maintained?

SuperhotGeo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SuperhotGeo MCP server?

VerifyMCP ran 12 checks on SuperhotGeo, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SuperhotGeo: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://superhotgeo.com/mcp
- Website: https://superhotgeo.com/for-ai.html
- Changelog RSS feed: https://verifymcp.io/servers/com-superhotgeo-superhotgeo/superhotgeo.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-superhotgeo-superhotgeo/superhotgeo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-superhotgeo-superhotgeo/superhotgeo.json
- HTML version of this page: https://verifymcp.io/servers/com-superhotgeo-superhotgeo/superhotgeo