NOAA CO-OPS MCP Server
PYPI · COOPS-MCP · SCANNED SEP 20
NOAA CO-OPS tides, water levels, currents, and meteorological data
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
pypi · coops-mcp
claude mcp add oceanmodeling-coops-mcp -- uvx coops-mcp
{
"mcpServers": {
"oceanmodeling-coops-mcp": {
"command": "uvx",
"args": [
"coops-mcp"
]
}
}
} {
"servers": {
"oceanmodeling-coops-mcp": {
"command": "uvx",
"args": [
"coops-mcp"
]
}
}
} codex mcp add oceanmodeling-coops-mcp -- uvx coops-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"oceanmodeling-coops-mcp": {
"type": "local",
"command": [
"uvx",
"coops-mcp"
],
"enabled": true
}
}
} openclaw mcp add oceanmodeling-coops-mcp --command uvx --arg coops-mcp
mcp_servers:
oceanmodeling-coops-mcp:
command: "uvx"
args: ["coops-mcp"] {
"McpServers": {
"oceanmodeling-coops-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"coops-mcp"
]
}
}
} assistant mcp add oceanmodeling-coops-mcp -t stdio -c uvx -a coops-mcp
{
"mcpServers": {
"oceanmodeling-coops-mcp": {
"command": "uvx",
"args": [
"coops-mcp"
]
}
}
} 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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +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.
- 10 Sept 26 +3
- Stability: unverified → 0.20 ▲ functional
- 5 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Sept 26 48
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 20 Sept 2026 · Analysed pypi/coops-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
coops_find_nearest_stations ~181
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]).
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| limit | integer | – | – |
| longitude | number | yes | – |
| radius_km | number | – | – |
| response_format | string | – | – |
| station_type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_currents ~323
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.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_date | – | – | – |
| bin_num | – | – | – |
| date | – | – | – |
| end_date | – | – | – |
| max_records | integer | – | – |
| product | – | – | – |
| response_format | string | – | – |
| station_id | string | yes | – |
| time_zone | – | – | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_datums ~106
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).
| Name | Type | Req | Description |
|---|---|---|---|
| station_id | string | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_extreme_water_levels ~118
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).
| Name | Type | Req | Description |
|---|---|---|---|
| datum | – | – | – |
| station_id | string | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_flood_stats ~133
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).
| Name | Type | Req | Description |
|---|---|---|---|
| datum | – | – | – |
| station_id | string | yes | – |
| units | – | – | – |
| year | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_meteorological ~318
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.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_date | – | – | – |
| date | – | – | – |
| end_date | – | – | – |
| interval | – | – | – |
| max_records | integer | – | – |
| product | – | yes | – |
| response_format | string | – | – |
| station_id | string | yes | – |
| time_zone | – | – | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_peak_storm_events ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| datum | – | – | – |
| station_id | string | yes | – |
| units | – | – | – |
| year | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_sea_level_trends ~72
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).
| Name | Type | Req | Description |
|---|---|---|---|
| station_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_station ~117
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).
| Name | Type | Req | Description |
|---|---|---|---|
| expand | – | – | – |
| station_id | string | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_tide_predictions ~331
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.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_date | string | yes | – |
| datum | – | – | – |
| end_date | string | yes | – |
| interval | – | – | – |
| max_records | integer | – | – |
| response_format | string | – | – |
| station_id | string | yes | – |
| time_zone | – | – | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_get_water_levels ~383
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.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_date | – | – | – |
| date | – | – | – |
| datum | – | – | – |
| end_date | – | – | – |
| interval | – | – | – |
| max_records | integer | – | – |
| response_format | string | – | – |
| station_id | string | yes | – |
| time_zone | – | – | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
coops_list_stations ~129
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| state | – | – | – |
| station_type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.