# Noaa Ncei (npm · @pipeworx/mcp-noaa-ncei)

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

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-noaa-ncei/noaa-ncei-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-noaa-ncei/noaa-ncei-mcp)
- npm · `@pipeworx/mcp-noaa-ncei`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-noaa-ncei/pipeworx-mcp-noaa-ncei.md), [page](https://verifymcp.io/servers/pipeworx-io-noaa-ncei/pipeworx-mcp-noaa-ncei)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-noaa-ncei`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-noaa-ncei).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 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.

### Claude

```bash
claude mcp add pipeworx-io-noaa-ncei -- npx -y @pipeworx/mcp-noaa-ncei
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-noaa-ncei": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-noaa-ncei"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-noaa-ncei": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-noaa-ncei"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-noaa-ncei -- npx -y @pipeworx/mcp-noaa-ncei
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-noaa-ncei": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-noaa-ncei"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-noaa-ncei --command npx --arg -y --arg @pipeworx/mcp-noaa-ncei
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-noaa-ncei:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-noaa-ncei"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-noaa-ncei": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-noaa-ncei"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-noaa-ncei -t stdio -c npx -a -y @pipeworx/mcp-noaa-ncei
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-noaa-ncei": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-noaa-ncei"
      ]
    }
  }
}
```

## 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-05 (score 82, +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.

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 80, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 79, +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.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `ncei_daily_summaries` (~306 tokens)

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.

Input parameters:

- `dataTypes` (string): Comma-separated element codes, e.g. "TMAX,TMIN,PRCP,SNOW,AWND". Omit for every element the station reports.
- `dataset` (string): Access dataset id (default "daily-summaries"). Others: "global-summary-of-the-day", "global-summary-of-the-month", "normals-daily".
- `endDate` (string, required): Last day, YYYY-MM-DD
- `limit` (number): Max daily rows to return (default 400, max 5000)
- `startDate` (string, required): First day, YYYY-MM-DD
- `stations` (string, required): GHCN station id(s), comma-separated, e.g. "USW00023174" (LAX) or "USW00023174,USW00014922". Find them with ncei_station_search.
- `units` (string): "standard" (°F, inches — default) or "metric" (°C, mm)

### `ncei_station_search` (~210 tokens)

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.

Input parameters:

- `bbox` (string, required): Bounding box "minLon,minLat,maxLon,maxLat" (WGS84). Reordered to NCEI's north,west,south,east form for you.
- `dataTypes` (string): Comma-separated element codes the station must report, e.g. "TMAX,PRCP"
- `dataset` (string): Dataset id (default "daily-summaries")
- `endDate` (string): Latest date the station must cover, YYYY-MM-DD
- `limit` (number): Max stations to return (default 25, max 200)
- `startDate` (string): Earliest date the station must cover, YYYY-MM-DD

### `ncei_search_datasets` (~125 tokens)

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.

Input parameters:

- `limit` (number): Max datasets to return (default 10, max 100)
- `text` (string): Free-text search over dataset titles, descriptions and keywords, e.g. "precipitation", "hurricane", "sea ice"

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-noaa-ncei/pipeworx-mcp-noaa-ncei#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

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

### What did VerifyMCP test on the Noaa Ncei MCP server?

VerifyMCP ran 16 checks on Noaa Ncei, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-noaa-ncei
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-noaa-ncei
- Repository: https://github.com/pipeworx-io/mcp-noaa-ncei
- Website: https://pipeworx.io/packs/noaa-ncei
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-noaa-ncei/pipeworx-mcp-noaa-ncei.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-noaa-ncei/pipeworx-mcp-noaa-ncei/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-noaa-ncei/pipeworx-mcp-noaa-ncei.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-noaa-ncei/pipeworx-mcp-noaa-ncei