# NOAA CO-OPS MCP Server (pypi · coops-mcp)

NOAA CO-OPS tides, water levels, currents, and meteorological data

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `coops-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/oceanmodeling-coops-mcp/coops-mcp.md), [page](https://verifymcp.io/servers/oceanmodeling-coops-mcp/coops-mcp)

## Channel facts

- Registry: `pypi`
- Package: `coops-mcp`
- Version: `0.1.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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (MIT License) isn't a recognized OSI-approved license.
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2331 tokens (~194/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 CO-OPS MCP Server server?

NOAA CO-OPS MCP Server runs locally as a PyPI package, launched with uvx coops-mcp. 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 oceanmodeling-coops-mcp -- uvx coops-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "oceanmodeling-coops-mcp": {
      "command": "uvx",
      "args": [
        "coops-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "oceanmodeling-coops-mcp": {
      "command": "uvx",
      "args": [
        "coops-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add oceanmodeling-coops-mcp -- uvx coops-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oceanmodeling-coops-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "coops-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add oceanmodeling-coops-mcp --command uvx --arg coops-mcp
```

### Hermes

```yaml
mcp_servers:
  oceanmodeling-coops-mcp:
    command: "uvx"
    args: ["coops-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "oceanmodeling-coops-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "coops-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add oceanmodeling-coops-mcp -t stdio -c uvx -a coops-mcp
```

### Other

```json
{
  "mcpServers": {
    "oceanmodeling-coops-mcp": {
      "command": "uvx",
      "args": [
        "coops-mcp"
      ]
    }
  }
}
```

## 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-09-19 (score 70, +1)

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

### 2026-09-17 (score 69, +1)

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

### 2026-09-15 (score 68, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 52, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-12 (score 67, +1)

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

### 2026-09-10 (score 66, +3)

- [functional improvement] Stability: unverified → 0.20

### 2026-09-05 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-04 (score 48)

First indexed and scored.

## MCP tools (12)

### `coops_get_currents` (~323 tokens)

Retrieve current (water flow) observations or predictions from a CO-OPS currents station.

Note: Currents stations use alphanumeric IDs (e.g., 'cb1401'), not the 7-digit numeric IDs used for water level stations.

Args:
    station_id: CO-OPS currents station ID (e.g., 'cb1401').
    product: Data type — 'currents' for observations, 'currents_predictions' for predictions.
    begin_date: Start date (YYYY-MM-DD or YYYYMMDD).
    end_date: End date (YYYY-MM-DD or YYYYMMDD).
    date: Date shorthand — 'today', 'latest', or 'recent' (alternative to begin/end).
    units: Unit system — 'metric' or 'english' (default: metric).
    time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt).
    bin_num: Depth bin number for multi-bin stations (optional).
    response_format: Output format — 'markdown' (default) or 'json'.
    max_records: Cap on records returned (default 2000). Only the most
        recent max_records are kept, and the output flags any truncation.

Input parameters:

- `begin_date`
- `bin_num`
- `date`
- `end_date`
- `max_records` (integer)
- `product`
- `response_format` (string)
- `station_id` (string, required)
- `time_zone`
- `units`

Output parameters:

- `result` (string)

### `coops_get_extreme_water_levels` (~118 tokens)

Get extreme (record) water levels ever recorded at a CO-OPS station.

Returns the highest and lowest water levels on record with dates and values.

Args:
    station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).
    datum: Vertical datum reference (default: MHHW).
    units: Unit system — 'metric' or 'english' (default: metric).

Input parameters:

- `datum`
- `station_id` (string, required)
- `units`

Output parameters:

- `result` (string)

### `coops_get_flood_stats` (~133 tokens)

Get annual flood day counts and high tide flooding outlook for a CO-OPS station.

Combines data from the annual flood count and high tide flooding outlook endpoints.

Args:
    station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).
    year: Optional specific year to query.
    datum: Vertical datum reference (default: MHHW).
    units: Unit system — 'metric' or 'english' (default: metric).

Input parameters:

- `datum`
- `station_id` (string, required)
- `units`
- `year`

Output parameters:

- `result` (string)

### `coops_get_sea_level_trends` (~72 tokens)

Get sea level trend data for a CO-OPS station.

Returns the long-term linear sea level trend with confidence intervals.

Args:
    station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).

Input parameters:

- `station_id` (string, required)

Output parameters:

- `result` (string)

### `coops_get_peak_storm_events` (~120 tokens)

Get peak water level events (storm surges) recorded at a CO-OPS station.

Args:
    station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).
    datum: Vertical datum reference (default: MHHW).
    units: Unit system — 'metric' or 'english' (default: metric).
    year: Optional specific year to query.

Input parameters:

- `datum`
- `station_id` (string, required)
- `units`
- `year`

Output parameters:

- `result` (string)

### `coops_get_datums` (~106 tokens)

Get tidal datum values for a CO-OPS station.

Returns datum elevations (MLLW, MHHW, MSL, MHW, MLW, etc.) relative to station datum.

Args:
    station_id: CO-OPS station ID (e.g., '9414290' for San Francisco, CA).
    units: Unit system — 'metric' or 'english' (default: metric).

Input parameters:

- `station_id` (string, required)
- `units`

Output parameters:

- `result` (string)

### `coops_get_meteorological` (~318 tokens)

Retrieve meteorological observations from a CO-OPS station.

Args:
    station_id: CO-OPS station ID (e.g., '8724580' for Key West, FL).
    product: Met data type — 'wind', 'air_temperature', 'water_temperature', 'air_pressure', 'humidity', 'conductivity', 'salinity', 'visibility', or 'air_gap'.
    begin_date: Start date (YYYY-MM-DD or YYYYMMDD).
    end_date: End date (YYYY-MM-DD or YYYYMMDD).
    date: Date shorthand — 'today', 'latest', or 'recent' (alternative to begin/end).
    units: Unit system — 'metric' or 'english' (default: metric).
    interval: Data interval — '6' (6-min) or 'h' (hourly).
    time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt).
    response_format: Output format — 'markdown' (default) or 'json'.
    max_records: Cap on records returned (default 2000). Only the most
        recent max_records are kept, and the output flags any truncation.

Input parameters:

- `begin_date`
- `date`
- `end_date`
- `interval`
- `max_records` (integer)
- `product` (required)
- `response_format` (string)
- `station_id` (string, required)
- `time_zone`
- `units`

Output parameters:

- `result` (string)

### `coops_list_stations` (~129 tokens)

List CO-OPS stations, optionally filtered by type and/or state.

Args:
    station_type: Filter by station type (e.g., 'waterlevels', 'currentpredictions', 'waterlevelsandmet').
    state: Filter by US state (2-letter code, e.g., 'NY', 'FL').
    limit: Maximum number of stations to return (default 50).
    offset: Number of stations to skip for pagination (default 0).

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `state`
- `station_type`

Output parameters:

- `result` (string)

### `coops_get_station` (~117 tokens)

Get detailed information for a specific CO-OPS station.

Args:
    station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).
    expand: Optional list of resources to include: 'details', 'sensors', 'datums', 'floodlevels', 'harcon', 'benchmarks'.
    units: Unit system — 'metric' or 'english' (default: metric).

Input parameters:

- `expand`
- `station_id` (string, required)
- `units`

Output parameters:

- `result` (string)

### `coops_find_nearest_stations` (~181 tokens)

Find CO-OPS stations nearest to a geographic coordinate.

Args:
    latitude: Latitude in decimal degrees (e.g., 40.7).
    longitude: Longitude in decimal degrees (e.g., -74.0).
    radius_km: Search radius in kilometers (default 50).
    station_type: Optional filter by station type (e.g., 'waterlevels').
    limit: Maximum number of stations to return (default 5).
    response_format: Output format — 'markdown' (default) or 'geojson'
        (a FeatureCollection of Point features, coordinates [lon, lat]).

Input parameters:

- `latitude` (number, required)
- `limit` (integer)
- `longitude` (number, required)
- `radius_km` (number)
- `response_format` (string)
- `station_type`

Output parameters:

- `result` (string)

### `coops_get_water_levels` (~383 tokens)

Retrieve observed water level data from a CO-OPS station.

Use begin_date/end_date for a date range, or date='today'/'latest'/'recent' for shortcuts.
Max range is 365 days per request.

Args:
    station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).
    begin_date: Start date (YYYY-MM-DD or YYYYMMDD format).
    end_date: End date (YYYY-MM-DD or YYYYMMDD format).
    date: Date shorthand — 'today', 'latest', or 'recent' (alternative to begin/end).
    datum: Vertical datum reference (default: MLLW). Options: MLLW, MHHW, MSL, NAVD, STND, MHW, MLW, MTL.
    units: Unit system — 'metric' or 'english' (default: metric).
    interval: Data interval — '6' (6-min), 'h' (hourly), 'hilo' (high/low only). Default is 6-min.
    time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt).
    response_format: Output format — 'markdown' (default) or 'json'.
    max_records: Cap on records returned (default 2000). A long 6-min range
        is tens of thousands of points; only the most recent max_records are
        kept, and the output flags any truncation.

Input parameters:

- `begin_date`
- `date`
- `datum`
- `end_date`
- `interval`
- `max_records` (integer)
- `response_format` (string)
- `station_id` (string, required)
- `time_zone`
- `units`

Output parameters:

- `result` (string)

### `coops_get_tide_predictions` (~331 tokens)

Retrieve tide predictions for a CO-OPS station.

Predictions are based on harmonic constituents — available for most water level stations.
Max range: 365 days (or 3650 days for high/low interval).

Args:
    station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).
    begin_date: Start date (YYYY-MM-DD or YYYYMMDD format).
    end_date: End date (YYYY-MM-DD or YYYYMMDD format).
    datum: Vertical datum reference (default: MLLW).
    units: Unit system — 'metric' or 'english' (default: metric).
    interval: Prediction interval — '6' (6-min), 'h' (hourly), 'hilo' (high/low only). Default is 6-min.
    time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt).
    response_format: Output format — 'markdown' (default) or 'json'.
    max_records: Cap on predictions returned (default 2000). A long 6-min
        range is tens of thousands of points; only the most recent
        max_records are kept, and the output flags any truncation.

Input parameters:

- `begin_date` (string, required)
- `datum`
- `end_date` (string, required)
- `interval`
- `max_records` (integer)
- `response_format` (string)
- `station_id` (string, required)
- `time_zone`
- `units`

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/oceanmodeling-coops-mcp/coops-mcp#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 52
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 63
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 63
- 2026-09-05: 63
- 2026-09-04: 48

## Common questions

### What is the NOAA CO-OPS MCP Server server?

NOAA CO-OPS MCP Server is listed in the public MCP registry as io.github.oceanmodeling/coops-mcp. NOAA CO-OPS tides, water levels, currents, and meteorological data. This page covers its PyPI package (coops-mcp).

### Is the NOAA CO-OPS MCP Server server safe to use?

NOAA CO-OPS MCP Server scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 CO-OPS MCP Server server expose?

NOAA CO-OPS MCP Server exposes 12 tools: coops_get_currents, coops_get_extreme_water_levels, coops_get_flood_stats, coops_get_sea_level_trends, coops_get_peak_storm_events, and 7 more. Their descriptions and schemas cost roughly 2,331 tokens of context every time the server is loaded.

### Is the NOAA CO-OPS MCP Server server still maintained?

NOAA CO-OPS MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/coops-mcp/
- Socket report: https://socket.dev/pypi/package/coops-mcp
- Repository: https://github.com/oceanmodeling/ocean-mcp
- Changelog RSS feed: https://verifymcp.io/servers/oceanmodeling-coops-mcp/coops-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/oceanmodeling-coops-mcp/coops-mcp.json
- HTML version of this page: https://verifymcp.io/servers/oceanmodeling-coops-mcp/coops-mcp