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.

ERDDAP MCP Server

PYPI · ERDDAP-MCP · SCANNED OCT 4

Access ocean data from 80+ ERDDAP servers worldwide

Available components

76 Trust /100
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
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to oceanmodeling/ocean-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1126 tokens (~187/item across 6 items; 6 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the ERDDAP MCP Server server?

ERDDAP MCP Server runs locally as a PyPI package, launched with uvx erddap-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · erddap-mcp

# add to Claude Code
claude mcp add oceanmodeling-erddap-mcp -- uvx erddap-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "oceanmodeling-erddap-mcp": {
      "command": "uvx",
      "args": [
        "erddap-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "oceanmodeling-erddap-mcp": {
      "command": "uvx",
      "args": [
        "erddap-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add oceanmodeling-erddap-mcp -- uvx erddap-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oceanmodeling-erddap-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "erddap-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add oceanmodeling-erddap-mcp --command uvx --arg erddap-mcp
# ~/.hermes/config.yaml
mcp_servers:
  oceanmodeling-erddap-mcp:
    command: "uvx"
    args: ["erddap-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "oceanmodeling-erddap-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "erddap-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add oceanmodeling-erddap-mcp -t stdio -c uvx -a erddap-mcp
// mcp.json
{
  "mcpServers": {
    "oceanmodeling-erddap-mcp": {
      "command": "uvx",
      "args": [
        "erddap-mcp"
      ]
    }
  }
}
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.

  • 1 Oct 26 76

    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 4 Oct 2026 · Analysed pypi/erddap-mcp@0.1.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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo oceanmodeling/ocean-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/oceanmodeling/ocean-mcp/.github/workflows/publish.yml@refs/tags/erddap-mcp-v0.1.1
Rekor log index 3034671120
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ed21b2ce4752d5334374afb26ddfde3044259aba651ced30ec8b61416d4e9cf1

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,126 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
erddap_get_all_datasets ~164

List all datasets available on a specific ERDDAP server. Args: server_url: ERDDAP server URL (default: CoastWatch West Coast). protocol: Filter by protocol — 'griddap' or 'tabledap' (optional). institution: Filter by institution name (optional, case-insensitive). search_text: Filter by text in title or summary (optional, case-insensitive). limit: Maximum number of datasets to return (default 50). offset: Number of datasets to skip for pagination (default 0).

NameTypeReqDescription
institution–––
limitinteger––
offsetinteger––
protocol–––
search_text–––
server_urlstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

erddap_get_dataset_info ~103

Get detailed metadata for an ERDDAP dataset — variables, dimensions, attributes, time/spatial coverage. Args: server_url: ERDDAP server URL (e.g., 'https://coastwatch.pfeg.noaa.gov/erddap'). dataset_id: ERDDAP dataset identifier (e.g., 'erdMH1chlamday').

NameTypeReqDescription
dataset_idstringyes–
server_urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

erddap_get_griddap_data ~380

Retrieve gridded data from an ERDDAP griddap dataset with dimension subsetting. Args: server_url: ERDDAP server URL (e.g., 'https://coastwatch.pfeg.noaa.gov/erddap'). dataset_id: ERDDAP dataset identifier (e.g., 'erdMH1chlamday'). variables: List of variable names to retrieve (default: first data variable). time_range: Time range as [start, stop] (e.g., ['2024-01-01T00:00:00Z', '2024-01-31T00:00:00Z']). Use same value for single time step. latitude_range: Latitude range as [min, max] (e.g., [36.0, 38.0]). longitude_range: Longitude range as [min, max] (e.g., [-123.0, -121.0]). depth_range: Depth/altitude range as [min, max] (optional, for datasets with depth dimension). stride: Step size for subsetting (default 1). Increase to reduce data volume. response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on JSON rows returned (default 2000). The first max_records grid points are kept and the JSON flags any truncation. (Markdown is already capped at 100 rows.)

NameTypeReqDescription
dataset_idstringyes–
depth_range–––
latitude_range–––
longitude_range–––
max_recordsinteger––
response_formatstring––
server_urlstringyes–
strideinteger––
time_range–––
variables–––
NameTypeReqDescription
resultstringyes–

No examples provided.

erddap_get_tabledap_data ~252

Retrieve tabular data from an ERDDAP tabledap dataset with constraint filtering. Args: server_url: ERDDAP server URL (e.g., 'https://coastwatch.pfeg.noaa.gov/erddap'). dataset_id: ERDDAP dataset identifier. variables: List of variable names to retrieve (default: all). constraints: Dict of constraints, e.g. {"time>=": "2024-01-01", "latitude>=": 38.0, "station=": "46013"}. limit: Maximum number of rows to return (default 1000). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on JSON rows returned (default 2000). The first max_records rows are kept and the JSON flags any truncation. (Markdown is already capped at 100 rows.)

NameTypeReqDescription
constraints–––
dataset_idstringyes–
limitinteger––
max_recordsinteger––
response_formatstring––
server_urlstringyes–
variables–––
NameTypeReqDescription
resultstringyes–

No examples provided.

erddap_list_servers ~70

List known ERDDAP servers from the built-in registry. Args: region: Filter by region (e.g., 'US East Coast', 'Pacific', 'Global'). keyword: Filter by keyword matching name, focus, or region.

NameTypeReqDescription
keyword–––
region–––
NameTypeReqDescription
resultstringyes–

No examples provided.

erddap_search_datasets ~157

Search for datasets on an ERDDAP server using free-text search. Args: search_for: Search terms (e.g., 'sea surface temperature', 'chlorophyll', 'wind'). server_url: ERDDAP server URL (default: CoastWatch West Coast). protocol: Filter by protocol — 'griddap' or 'tabledap' (optional). items_per_page: Number of results per page (default 20, max 1000). page: Page number for pagination (default 1).

NameTypeReqDescription
items_per_pageinteger––
pageinteger––
protocol–––
search_forstringyes–
server_urlstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the ERDDAP MCP Server server?

ERDDAP MCP Server is listed in the public MCP registry as io.github.oceanmodeling/erddap-mcp. Access ocean data from 80+ ERDDAP servers worldwide. This page covers its PyPI package (erddap-mcp).

Is the ERDDAP MCP Server server safe to use?

ERDDAP MCP Server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. 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 ERDDAP MCP Server server expose?

ERDDAP MCP Server exposes 6 tools: erddap_get_griddap_data, erddap_get_dataset_info, erddap_list_servers, erddap_search_datasets, erddap_get_all_datasets, erddap_get_tabledap_data. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.

Is the ERDDAP MCP Server server still maintained?

ERDDAP MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 October 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 ERDDAP MCP Server server under?

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