NOAA CO-OPS MCP Server
NOAA CO-OPS tides, water levels, currents, and meteorological data
10 stars39 downloads/wk
Reviews
Write oneNobody has reviewed NOAA CO-OPS MCP Server yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
NOAA CO-OPS MCP Server tools (12)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
coops_find_nearest_stationsFind CO-OPS stations nearest to a geographic coordinate.
coops_get_currentsRetrieve current (water flow) observations or predictions from a CO-OPS currents station.
coops_get_datumsGet tidal datum values for a CO-OPS station.
coops_get_extreme_water_levelsGet extreme (record) water levels ever recorded at a CO-OPS station.
coops_get_flood_statsGet annual flood day counts and high tide flooding outlook for a CO-OPS station.
coops_get_meteorologicalRetrieve meteorological observations from a CO-OPS station.
coops_get_peak_storm_eventsGet peak water level events (storm surges) recorded at a CO-OPS station.
coops_get_sea_level_trendsGet sea level trend data for a CO-OPS station.
coops_get_stationGet detailed information for a specific CO-OPS station.
coops_get_tide_predictionsRetrieve tide predictions for a CO-OPS station.
coops_get_water_levelsRetrieve observed water level data from a CO-OPS station.
coops_list_stationsList CO-OPS stations, optionally filtered by type and/or state.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- Code scan15 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How NOAA CO-OPS MCP Server compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 94/100
- higher than 96% of 48,243 servers
- Tools
- 12
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 10
- more than 88% of 28,706 servers
- Downloads a week
- 39
- more than 29% of 12,306 servers with a package
What its tools let an agent do: 12 read
Install NOAA CO-OPS MCP Server in Claude Code, Cursor or VS Code
claude mcp add coops-mcp -- uvx coops-mcp
What the publisher says
From the NOAA CO-OPS MCP Server repository's README, as published. We do not edit it. Read it on GitHub
OceanMCP
A monorepo of independently installable MCP servers for ocean and coastal data workflows.
Servers
No API keys required for the data servers — all servers above use free, publicly available datasets. The exceptions are hpc-system-mcp and ufs-runner-mcp (below), which require actual NOAA RDHPCS cluster access and, in ufs-runner-mcp's case, submit real Slurm jobs.
Additional servers live in this repo but are not yet published to PyPI (install from source): vdatum-mcp (vertical datum conversion), hpc-system-mcp and ufs-runner-mcp (NOAA RDHPCS / UFS-Coastal HPC workflows — require cluster access), and alert-mcp (CO-OPS threshold alerting).
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
NOAA CO-OPS MCP Server: common questions
- Is NOAA CO-OPS MCP Server safe?
- Yes, by our scan: it is graded A (94/100). Read the NOAA CO-OPS MCP Server safety report
- How do I install NOAA CO-OPS MCP Server?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does NOAA CO-OPS MCP Server need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is NOAA CO-OPS MCP Server maintained?
- The last commit was 22 days ago (2026-10-14). The latest release is v0.1.1.
- How does NOAA CO-OPS MCP Server compare with other MCP servers?
- safety score 94/100 (higher than 96% of 48,243 servers); tools 12 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.