Home / MCP registry index / io.github.RyanCardin15/noaa-tides-and-currents-mcp

NOAA Tides and Currents

io.github.RyanCardin15/noaa-tides-and-currents-mcp in the official MCP registry. Endpoint https://perigeetides.com/mcp. Source: github.com/RyanCardin15/Perigee-Tides.

The registry describes it as: NOAA tides and currents: water levels, tide predictions, currents, met data, flooding, sun and moon

We read its 26 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http noaa-tides-and-currents-mcp https://perigeetides.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "noaa-tides-and-currents-mcp": {
      "url": "https://perigeetides.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"noaa-tides-and-currents-mcp","type":"http","url":"https://perigeetides.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

noaa_get_water_levels noaa_get_water_level_summaries noaa_get_tide_predictions noaa_get_currents noaa_get_current_predictions noaa_get_meteorological_data noaa_search_stations noaa_find_nearest_stations noaa_get_station_info noaa_get_station_datums noaa_get_harmonic_constituents noaa_get_prediction_offsets noaa_get_sea_level_trends noaa_get_sea_level_rise_projections noaa_get_extreme_water_levels noaa_get_top_ten_water_levels noaa_get_high_tide_flooding astro_get_moon_phase astro_get_next_moon_phase astro_get_sun_times astro_get_sun_position astro_get_next_sun_event nws_get_wind_forecast nws_get_marine_forecast noaa_get_reference_guide perigee_whoami

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ryancardin15-noaa-tides-and-currents-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ryancardin15-noaa-tides-and-currents-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.