Gistemp
NPM · @PIPEWORX/MCP-GISTEMP · 2 COMPONENTS
GISTEMP MCP — NASA Goddard Institute for Space Studies Surface Temperature Analysis (free, no auth)
Available components
Last scanned (6 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-gistemp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 508 tokens (~169/item across 3 items; 3 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 Management23
- Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
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 · Analysed npm/@pipeworx/mcp-gistemp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-gistemp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-gistemp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637324634 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ccbbde593623765f675be50134816e85805a50f2c01181e33cfc1179b2ddb6a2b1e8e0dac8c5a39fcd347526928af4d4fe5025aab992490d86362a5ac |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_latest_anomaly ~109
Most recent NASA GISTEMP global land+ocean monthly anomaly, plus how it ranks against history. Returns the latest available month, the anomaly value (degrees C from 1951-1980 baseline), the rank of that value among all same-month observations since 1880, and a 12-month trailing mean. Cheaper than get_temperature_anomaly when you only need "what is the current reading and is it unusual."
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | Default global_land_ocean. |
No output schema declared.
No examples provided.
get_temperature_anomaly ~196
NASA GISTEMP surface temperature anomaly time series (degrees C from 1951-1980 baseline). Pick a region (global_land_ocean, global_land_only, northern_hemisphere, southern_hemisphere) and get monthly + annual + seasonal values back. Use for climate bets ("will 2026 be the hottest year on record"), trend comparisons, or cross-source consistency checks against HadCRUT5/Berkeley Earth. Annual frequency returns one row per year (Jan-Dec mean); monthly returns Jan..Dec per year.
| Name | Type | Req | Description |
|---|---|---|---|
| end_year | number | – | Last year to include (default current year). |
| frequency | string | – | annual (one row per year) or monthly (12 rows per year). Default annual. |
| region | string | – | Which region to fetch. Default global_land_ocean. |
| start_year | number | – | First year to include (default 1880, the dataset start). |
No output schema declared.
No examples provided.
get_zonal_anomalies ~150
NASA GISTEMP annual zonal anomalies (degrees C from 1951-1980 baseline) for 8 latitude bands: global, Northern Hemisphere, Southern Hemisphere, 24N-90N, 24S-24N (tropics), 90S-24S, 64N-90N (Arctic), 44S-24S, etc. Use for regional climate bets ("will the Arctic warm faster than the tropics in 2026") or bets framed around polar amplification.
| Name | Type | Req | Description |
|---|---|---|---|
| end_year | number | – | Last year to include (default current year). |
| start_year | number | – | First year to include (default 1880). |
No output schema declared.
No examples provided.
How do I install the Gistemp MCP server?
Gistemp runs locally as an npm package, launched with npx -y @pipeworx/mcp-gistemp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-gistemp
claude mcp add pipeworx-io-gistemp -- npx -y @pipeworx/mcp-gistemp
What is the Gistemp MCP server?
Gistemp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/gistemp. GISTEMP MCP, NASA Goddard Institute for Space Studies Surface Temperature Analysis (free, no auth). This page covers its npm package (@pipeworx/mcp-gistemp).
Is the Gistemp MCP server safe to use?
Gistemp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Gistemp MCP server expose?
Gistemp exposes 3 tools: get_temperature_anomaly, get_latest_anomaly, get_zonal_anomalies. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.
Is the Gistemp MCP server still maintained?
Gistemp 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 licence is the Gistemp MCP server under?
Gistemp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.