A
licenseNot graded
qualityB
maintenanceMCP server that provides access to NOAA Tides & Currents data including tide predictions, water levels, currents, and meteorological observations.
26 npm
MIT
noaa-tidesandcurrents-mcp
by RyanCardin15
Related Servers
Alternatives to noaa-tidesandcurrents-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that provides tide predictions, station lookup, and tidal event alerts for US coastal locations using live NOAA data.-
- FlicenseNot gradedqualityDmaintenanceMinimal MCP server exposing tools for kitesurfing forecasts (wind and waves via Open-Meteo) and tide predictions (via NOAA CO-OPS).-
- AlicenseNot gradedqualityAmaintenanceFind NOAA tide stations and NDBC buoys, fetch tide predictions, water levels, tidal currents, and live buoy conditions via MCP.338 npm1Apache 2.0
- FlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that provides US weather forecasts and active alerts using the National Weather Service API.2-
- AlicenseBqualityFmaintenanceA Model Context Protocol server that provides tools to fetch weather alerts for US states and forecasts based on latitude/longitude coordinates using the US National Weather Service API.2159 npm1MIT
TDQS
A4.1/5.0
Scored across 25 tools
Disambiguation4/5
Most tools target distinct resources and actions, but several flood/water-level tools overlap conceptually (e.g. water levels vs summaries, high tide flooding vs extreme water levels vs top ten water levels). Observed vs predicted distinctions also require reading descriptions. The descriptions help substantially, so boundaries are mostly clear rather than perfect.
Naming Consistency5/5
All tool names use snake_case and follow a prefix_verb_noun pattern with coherent noaa_, astro_, and nws_ namespaces. Variations like search_stations, find_nearest_stations, and get_* remain predictable and consistent.
Tool Count4/5
25 tools is on the high side for a single server, but the breadth spans NOAA observations, predictions, summaries, station metadata, astronomy, and NWS forecasts. Each tool appears to serve a distinct product rather than duplicating functionality, making the count slightly heavy but reasonable.
Completeness5/5
The surface covers station discovery, metadata, datums, harmonic constituents, prediction offsets, observations, predictions, summaries, sea level trends/projections, flooding/extremes, plus astronomy and forecast companions. No obvious lifecycle gap is apparent for the stated tides-and-currents domain.
Maintenance
ActivityMaintained
ResponsivenessResponsive