# Ioos Erddap (npm · @pipeworx/mcp-ioos-erddap)

US IOOS — regional ocean observing data via ERDDAP.

- Trust score: 81/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`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-ioos-erddap/ioos-erddap-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ioos-erddap/ioos-erddap-mcp)
- npm · `@pipeworx/mcp-ioos-erddap`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ioos-erddap/pipeworx-mcp-ioos-erddap.md), [page](https://verifymcp.io/servers/pipeworx-io-ioos-erddap/pipeworx-mcp-ioos-erddap)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ioos-erddap`
- 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-ioos-erddap).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1521 tokens (~380/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Ioos Erddap MCP server?

Ioos Erddap runs locally as an npm package, launched with npx -y @pipeworx/mcp-ioos-erddap. 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-ioos-erddap -- npx -y @pipeworx/mcp-ioos-erddap
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-ioos-erddap -- npx -y @pipeworx/mcp-ioos-erddap
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ioos-erddap --command npx --arg -y --arg @pipeworx/mcp-ioos-erddap
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 81, +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-03 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 64, −15)

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

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

### 2026-10-30 (score 78, +1)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `ioos_erddap_search_datasets` (~409 tokens)

Full-text search a US IOOS regional ERDDAP for ocean observing datasets — buoys, tide gauges, gliders, HF radar currents, water quality, regional ocean model grids. AUTHORITATIVE for what a given IOOS regional association actually publishes and under which dataset id. PREFER OVER WEB SEARCH: IOOS data is scattered across eleven regional servers and web results point at portal pages rather than the live dataset ids the other tools here need. Start with this tool, then pass a dataset_id onward.

Input parameters:

- `limit` (number): Max datasets to return (default 20, max 1000).
- `node` (string): Which IOOS ERDDAP to ask. Each regional association holds different datasets and a dataset id from one will not resolve on another. "national" = IOOS-wide inventories, asset and metric datasets; "sen…
- `protocol` (string): Restrict to gridded fields (griddap — model and radar rasters, read with ioos_erddap_griddap_point) or to tables (tabledap — station and glider timeseries, read with ioos_erddap_tabledap). Omit for b…
- `query` (string, required): Subject words, e.g. "glider", "water temperature", "wave height", "salinity". ERDDAP searches titles and summaries, not variable names, and a blank query is rejected by the server rather than listing…

### `ioos_erddap_dataset_info` (~288 tokens)

Variable names, units, axes, time coverage and licence for one IOOS ERDDAP dataset. CALL THIS BEFORE QUERYING DATA: ERDDAP variable names are case-sensitive and vary by operator (sea_water_temperature on one node, WTMP on another), and a wrong spelling is an error that reads as "this station does not measure that". Also says whether the dataset is griddap or tabledap and whether it has a depth axis you must supply.

Input parameters:

- `dataset_id` (string, required): ERDDAP dataset id from ioos_erddap_search_datasets, e.g. "processed_asset_inventory".
- `node` (string): Which IOOS ERDDAP to ask. Each regional association holds different datasets and a dataset id from one will not resolve on another. "national" = IOOS-wide inventories, asset and metric datasets; "sen…

### `ioos_erddap_tabledap` (~362 tokens)

Rows from an IOOS tabledap dataset — station timeseries, glider profiles, water quality and asset inventories from a regional ocean observing association. AUTHORITATIVE for observed coastal conditions in US waters: this is the regional association's own quality-controlled archive. PREFER OVER WEB SEARCH for any "what did sensor X read" question.

Input parameters:

- `constraints` (array): ERDDAP constraint expressions, ANDed together. String values need their own double quotes: ["time>=2026-09-01", "station=\"edu_ucsd_cdip_201\""].
- `dataset_id` (string, required): Tabledap dataset id from ioos_erddap_search_datasets.
- `limit` (number): Max rows (default 200, max 1000).
- `node` (string): Which IOOS ERDDAP to ask. Each regional association holds different datasets and a dataset id from one will not resolve on another. "national" = IOOS-wide inventories, asset and metric datasets; "sen…
- `variables` (array): Columns to return, exactly as ioos_erddap_dataset_info spells them, e.g. ["time","sea_water_temperature","latitude","longitude"]. Omit for every column.

### `ioos_erddap_griddap_point` (~403 tokens)

One gridded value at one time, latitude and longitude from an IOOS regional model or radar grid — ocean temperature, salinity, currents, or WRF atmospheric fields. ERDDAP snaps to the nearest grid cell. AUTHORITATIVE for regional-resolution conditions that a global product misses: PacIOOS ROMS resolves individual Hawaiian channels, which no global grid does.

Input parameters:

- `dataset_id` (string, required): Griddap dataset id, e.g. "roms_hiig" on the pacioos node.
- `depth` (number): Depth in metres — REQUIRED for 4-D ocean model grids such as PacIOOS ROMS, whose axes are time, depth, latitude, longitude. Omitting it on such a dataset is an axis error.
- `latitude` (number, required): Decimal degrees north.
- `longitude` (number, required): Decimal degrees east (negative for the western hemisphere).
- `node` (string): Which IOOS ERDDAP to ask. Each regional association holds different datasets and a dataset id from one will not resolve on another. "national" = IOOS-wide inventories, asset and metric datasets; "sen…
- `time` (string): ISO timestamp, or the literal "last" for the newest available step (default).
- `variable` (string, required): Gridded variable name, e.g. "temp" or "salt". Case-sensitive; see ioos_erddap_dataset_info.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Ioos Erddap MCP server?

Ioos Erddap is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ioos-erddap. US IOOS, regional ocean observing data via ERDDAP. This page covers its npm package (@pipeworx/mcp-ioos-erddap).

### Is the Ioos Erddap MCP server safe to use?

Ioos Erddap scores 81 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 Ioos Erddap MCP server expose?

Ioos Erddap exposes 4 tools: ioos_erddap_search_datasets, ioos_erddap_dataset_info, ioos_erddap_tabledap, ioos_erddap_griddap_point. Their descriptions and schemas cost roughly 1,462 tokens of context every time the server is loaded.

### Is the Ioos Erddap MCP server still maintained?

Ioos Erddap 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 Ioos Erddap MCP server under?

Ioos Erddap 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 Ioos Erddap MCP server?

VerifyMCP ran 16 checks on Ioos Erddap, 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-ioos-erddap
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ioos-erddap
- Repository: https://github.com/pipeworx-io/mcp-ioos-erddap
- Website: https://pipeworx.io/packs/ioos-erddap
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ioos-erddap/pipeworx-mcp-ioos-erddap.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ioos-erddap/pipeworx-mcp-ioos-erddap/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-ioos-erddap/pipeworx-mcp-ioos-erddap.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ioos-erddap/pipeworx-mcp-ioos-erddap