Skip to content
External endpointresponds

noaa-marine-mcp-server

Find NOAA tide stations and NDBC buoys, fetch tide predictions, currents, and live conditions.

Endpoint URL
https://noaa-marine.caseyjhand.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
377 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.cyanheads/noaa-marine-mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
noaa-marine-mcp-server
Version
0.3.0
Capability keys
logging, resources, tools, prompts
Tool names
noaa_marine_find_stations, noaa_marine_get_tide_predictions, noaa_marine_get_water_level, noaa_marine_get_currents, noaa_marine_get_conditions, noaa_marine_get_current_profile, noaa_marine_get_ocean_observations
Instructions excerpt

US marine conditions via NOAA CO-OPS and NDBC. Start with noaa_marine_find_stations to resolve a location or name to station IDs, then call the appropriate data tool. CO-OPS provides tide predictions (noaa_marine_get_tide_predictions), observed water levels and storm surge (noaa_marine_get_water_level), and tidal-current predictions (noaa_marine_get_currents). NDBC provides live buoy conditions — waves, wind, sea-surface temp (noaa_marine_get_conditions), observed ocean-current depth profiles (noaa_marine_get_current_profile), and sub-surface water-column observations — temperature, salinity, dissolved oxygen and more (noaa_marine_get_ocean_observations). The two current tools are distinct: get_currents is CO-OPS tidal-current predictions (forecast), get_current_profile is NDBC observed depth-binned currents from an ADCP buoy. All water height data is referenced to MLLW by default (US nautical chart datum).

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 289ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 380ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 265ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 377ms