Ioos Erddap
NPM · @PIPEWORX/MCP-IOOS-ERDDAP · 2 COMPONENTS
US IOOS — regional ocean observing data via ERDDAP.
Available components
Last scanned (13 hours ago)
Scores higher than 69% 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-ioos-erddap). 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 Usability56
- AI-judged instruction clarity (good).Pass
- 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. 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 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.
- 3 Nov 26 +16
- 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
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 77
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-ioos-erddap@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-ioos-erddap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ioos-erddap/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637467196 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4f3439fadecb07fec3dc26245be2b084d53e7bf7cbff3fb0adcdd3d293d322ca77a11e7b0ed68b00235751161084c3d74aff1c6bc94996e10a184a69c |
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 →
ioos_erddap_dataset_info ~288
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | 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… |
No output schema declared.
No examples provided.
ioos_erddap_griddap_point ~403
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | 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 | yes | Decimal degrees north. |
| longitude | number | yes | 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 | yes | Gridded variable name, e.g. "temp" or "salt". Case-sensitive; see ioos_erddap_dataset_info. |
No output schema declared.
No examples provided.
ioos_erddap_search_datasets ~409
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
ioos_erddap_tabledap ~362
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-ioos-erddap
claude mcp add pipeworx-io-ioos-erddap -- npx -y @pipeworx/mcp-ioos-erddap
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.