tide-times-tide-tables-mcp
Related Servers
Alternatives to tide-times-tide-tables-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides NOAA tide predictions and observed water levels, allowing AI agents to query tide stations and current water level data.2 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server that provides tide predictions, station lookup, and tidal event alerts for US coastal locations using live NOAA data.-
- AlicenseNot gradedqualityBmaintenanceFind NOAA tide stations and NDBC buoys, fetch tide predictions, water levels, tidal currents, and live buoy conditions via MCP.225 npm3Apache 2.0
- AlicenseBqualityDmaintenanceFetches tide information for any location using latitude and longitude, providing detailed tide data including high/low tides and station information with automatic UTC time zone handling.119MIT
- FlicenseAqualityDmaintenanceProvides Canadian tide predictions from the IWLS API, enabling retrieval of 7-day tide forecasts and station listings for monitoring stations across Canada.4-
- AlicenseAqualityCmaintenanceProvides real-time water temperature and tide predictions for any lake, river, ocean, bay, or beach using NOAA, USGS, and other sources.173 PyPIMIT
TDQS
Scored across 4 tools
Each tool has a distinct role: full tide table, current state snapshot, filtered low-tide windows, and station lookup. The only adjacency is between tide_times and tide_now, which could initially be confused, but the descriptions clearly separate a forecast table from a real-time rising/falling reading.
All names are snake_case and readable, generally following a tide_/low_tide_ noun-topic style. The pattern isn't a strict verb_noun convention and low_tide_windows breaks the tide_ prefix, but the set remains predictable and coherent.
Four tools is well-scoped for a focused NOAA tide service; each tool earns its place by covering a genuinely different use case (table, now, low-tide planning, station resolution). No tool feels redundant or filler.
Coverage spans the core lifecycle: resolve a station, get a full table, check current state, and find actionable low-tide windows. Minor gaps exist, such as a high-tide/event window finder or tide curve data, but agents can derive high tides from tide_times.