MCP servers observed by Lowdown
io.github.RyanCardin15/noaa-tides-and-currents-mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 31 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.RyanCardin15/noaa-tides-and-currents-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.RyanCardin15/noaa-tides-and-currents-mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 26 → 31
What tools does it list?
31 tools on 2026-11-19:
astro_get_moon_phaseastro_get_next_moon_phaseastro_get_next_sun_eventastro_get_sun_positionastro_get_sun_timesnoaa_find_nearest_stationsnoaa_get_current_predictionsnoaa_get_currentsnoaa_get_extreme_water_levelsnoaa_get_harmonic_constituentsnoaa_get_high_tide_floodingnoaa_get_meteorological_datanoaa_get_prediction_offsetsnoaa_get_reference_guidenoaa_get_sea_level_rise_projectionsnoaa_get_sea_level_trendsnoaa_get_station_datumsnoaa_get_station_infonoaa_get_tide_predictionsnoaa_get_top_ten_water_levelsnoaa_get_water_level_summariesnoaa_get_water_levelsnoaa_search_stationsnws_get_marine_forecastnws_get_wind_forecastperigee_find_best_timeperigee_find_stationsperigee_get_conditionsperigee_get_sun_moonperigee_get_tidesperigee_whoami
MCP Registry declaration
- Registry name:
io.github.RyanCardin15/noaa-tides-and-currents-mcp - Declared version: 2.1.0
- Status: active
- Declared hosts:
perigeetides.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.RyanCardin15/noaa-tides-and-currents-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.RyanCardin15/noaa-tides-and-currents-mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.RyanCardin15/noaa-tides-and-currents-mcp -- npx -y @ryancardin/noaa-tides-currents-mcp-server
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).