SuperhotGeo
REMOTE · SUPERHOTGEO.COM
Superhot rock geothermal: well registry with failures at temperature, projects, research, RockLab.
Available components
Last scanned (15 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://superhotgeo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lineefficiency.com | CN=WR3,O=Google Trust Services,C=US | 18 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 19fb9acd7f4af12f0a039601837df5ba |
| SANs: lineefficiency.com, stresspatrol.com, onixeratechnologies.com, control.inemuri.cafe, reflection.ceo, homeworkhelpgpt.com, vericode.ai, workflow-zero.ai, www.iglesiacci.com.ar, bharatwealth.app, pasteableapp.com, www.mxmarhitektura.hr and 88 more | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of superhotgeo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| superhotgeo.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://superhotgeo.com/mcp | Verified | 200 | |
| http (plaintext) | http://superhotgeo.com/mcp | HTTPS enforced | 301 | https://superhotgeo.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_superhot ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question to ask. |
No output schema declared.
No examples provided.
fetch Fetch a SuperhotGeo record ~47
Fetch the full text of one record returned by `search`, with its canonical URL and source.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An id from `search`, formatted "<resource>:<recordId>". |
No output schema declared.
No examples provided.
get_resource ~39
Fetch a single SuperhotGeo record by resource and id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The record id. |
| resource | string | yes | Which collection. |
No output schema declared.
No examples provided.
list_resource ~301
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 25). |
| q | string | – | Optional keyword filter. |
| resource | string | yes | Which collection to list. |
No output schema declared.
No examples provided.
search Search SuperhotGeo ~155
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural-language or keyword query, e.g. "casing failure above 400 C" or "magma Krafla". |
No output schema declared.
No examples provided.
search_library ~61
Search SuperhotGeo's continuously curated library of superhot geothermal news, studies, journals, and resources.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 25). |
| query | string | yes | Keywords to match against title, description, author, or source. |
No output schema declared.
No examples provided.
search_wells Search the Superhot Well Registry ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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"). |
No output schema declared.
No examples provided.
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.
remote · superhotgeo.com
claude mcp add --transport http com-superhotgeo-superhotgeo 'https://superhotgeo.com/mcp'
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.