BC Water Tides MCP Server
Related Servers
Alternatives to BC Water Tides MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceFind NOAA tide stations and NDBC buoys, fetch tide predictions, water levels, tidal currents, and live buoy conditions via MCP.302 npm1Apache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides NOAA tide predictions and observed water levels, allowing AI agents to query tide stations and current water level data.2 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server that provides tide predictions, station lookup, and tidal event alerts for US coastal locations using live NOAA data.-
- 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
- FlicenseAqualityCmaintenanceEnables users to monitor active Canadian meteorological warnings and advisories, view national and provincial counts, check alerts near coordinates, and generate safety briefings and incident reports.4-
- AlicenseBqualityCmaintenanceProvides access to Hong Kong climate and weather data from the Hong Kong Observatory, including current conditions, forecasts, warnings, tides, and more.196MIT
TDQS
Scored across 4 tools
Most tools are clearly distinct: list_stations for discovery, plot_tide_forecast for visualization. get_tide_forecast and get_tide_forecast_pst overlap heavily as the same forecast data, but their descriptions explicitly differentiate UTC vs PST output, reducing confusion.
Tools follow a consistent verb_noun pattern (list_stations, get_tide_forecast, plot_tide_forecast). get_tide_forecast_pst introduces a timezone suffix modifier, which is a minor deviation but still predictable and readable.
Four tools is well-scoped for a tide forecast server: station discovery, UTC forecast data, PST-localized forecast data, and visualization. Each tool serves a distinct need without redundancy or bloat.
The core workflow is covered: discover stations, retrieve forecast data, localize it, and visualize it. Minor gaps exist, such as no option to specify a custom date range or fetch real-time observed water levels, but these are not core to the stated purpose.