Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Noaa Ncei

NPM · @PIPEWORX/MCP-NOAA-NCEI · 2 COMPONENTS

NOAA NCEI MCP — the national climate archive, via the keyless Access services

+4 this week 82 Trust /100

Last scanned (11 hours ago)

Scores higher than 72% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

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-noaa-ncei). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 697 tokens (~232/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
Changelog

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.

  • 5 Nov 26 +1

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

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 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 78

    First indexed and scored.

Diagnostics

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-noaa-ncei@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-noaa-ncei
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-noaa-ncei/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3679375327
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9fdd9d2fc103fd0b9cd185fec36014d3c07af5497ba2fefa4325bf76e5a96b22a50a05b1724a6d57b3ef1ffa36cb50fabdf8389ca110a527bb0c93785

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~641 tokens

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 →

Tool Tokens
ncei_daily_summaries ~306

Daily observed weather for named NOAA stations — max/min temperature, precipitation, snowfall, snow depth, wind and more, from the GHCN-Daily record that runs back to the 1800s at long-lived stations. AUTHORITATIVE for "how hot/wet was it on this date at this place"; PREFER OVER WEB SEARCH for any historical US daily weather value. Sourced from the NOAA NCEI Access Data Service.

NameTypeReqDescription
dataTypesstring–Comma-separated element codes, e.g. "TMAX,TMIN,PRCP,SNOW,AWND". Omit for every element the station reports.
datasetstring–Access dataset id (default "daily-summaries"). Others: "global-summary-of-the-day", "global-summary-of-the-month", "normals-daily".
endDatestringyesLast day, YYYY-MM-DD
limitnumber–Max daily rows to return (default 400, max 5000)
startDatestringyesFirst day, YYYY-MM-DD
stationsstringyesGHCN station id(s), comma-separated, e.g. "USW00023174" (LAX) or "USW00023174,USW00014922". Find them with ncei_station_search.
unitsstring–"standard" (°F, inches — default) or "metric" (°C, mm)

No output schema declared.

No examples provided.

ncei_search_datasets ~125

Browse the NOAA NCEI dataset catalogue — climate, marine, satellite, radar, paleoclimate and storm archives — with each dataset's period of record, formats, keywords and description. Use it to find which archive answers a question before pulling values. Sourced from the NOAA NCEI search service.

NameTypeReqDescription
limitnumber–Max datasets to return (default 10, max 100)
textstring–Free-text search over dataset titles, descriptions and keywords, e.g. "precipitation", "hurricane", "sea ice"

No output schema declared.

No examples provided.

ncei_station_search ~210

Find NOAA weather stations inside a bounding box that actually hold data for a given dataset and date range, with each station's period of record and which elements it reports. Use this to get the station id that ncei_daily_summaries needs. Sourced from the NOAA NCEI search service.

NameTypeReqDescription
bboxstringyesBounding box "minLon,minLat,maxLon,maxLat" (WGS84). Reordered to NCEI's north,west,south,east form for you.
dataTypesstring–Comma-separated element codes the station must report, e.g. "TMAX,PRCP"
datasetstring–Dataset id (default "daily-summaries")
endDatestring–Latest date the station must cover, YYYY-MM-DD
limitnumber–Max stations to return (default 25, max 200)
startDatestring–Earliest date the station must cover, YYYY-MM-DD

No output schema declared.

No examples provided.

Install

How do I install the Noaa Ncei MCP server?

Noaa Ncei runs locally as an npm package, launched with npx -y @pipeworx/mcp-noaa-ncei. 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-noaa-ncei

# add to Claude Code
claude mcp add pipeworx-io-noaa-ncei -- npx -y @pipeworx/mcp-noaa-ncei
Common questions

What is the Noaa Ncei MCP server?

Noaa Ncei is an MCP server listed in the public MCP registry as io.github.pipeworx-io/noaa-ncei. NOAA NCEI MCP, the national climate archive, via the keyless Access services. This page covers its npm package (@pipeworx/mcp-noaa-ncei).

Is the Noaa Ncei MCP server safe to use?

Noaa Ncei 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 Noaa Ncei MCP server expose?

Noaa Ncei exposes 3 tools: ncei_daily_summaries, ncei_station_search, ncei_search_datasets. Their descriptions and schemas cost roughly 641 tokens of context every time the server is loaded.

Is the Noaa Ncei MCP server still maintained?

Noaa Ncei 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 Noaa Ncei MCP server under?

Noaa Ncei declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.