mcpbeat

NOAA Tides and Currents MCP Server

io.github.RyanCardin15/noaa-tides-and-currents-mcp
not responding

NOAA Tides and Currents is listed as active in the registry but did not answer our last check. 114 installs a week from npm. It exposes 26 tools. Last commit 23 Jul 2026.

NOAA tides and currents: water levels, tide predictions, currents, met data, flooding, sun and moon

Installs per day peak 185 · avg 23 · +46% w/w
a month agotoday
Uptime history 39 hours of history · worst hour 0%
39 hours agonow
1.1%
Uptime 24h
1 of 91 checks
26
Tools
read from the server
535 ms
Response time
average over 24h
114
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add noaa-tides-and-currents-mcp --transport http https://perigeetides.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "noaa-tides-and-currents-mcp": {
      "url": "https://perigeetides.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.noaa-tides-and-currents-mcp]
url = "https://perigeetides.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "noaa-tides-and-currents-mcp": {
      "url": "https://perigeetides.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "noaa-tides-and-currents-mcp": {
      "url": "https://perigeetides.com/mcp"
    }
  }
}

Available tools 26

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

noaa
noaa_find_nearest_stations
Find the NOAA stations closest to a latitude/longitude point, sorted by distance. Use this to answer "what's the tide station near <place>?" — geocode the place to coordinates first, then call this. Filter by type to match the data you need (e.g. type "tidepredictions" before calling noaa_get_tide_predictions, "currents" before noaa_get_currents — current stations have different IDs than water-level stations). Distance is computed great-circle (Haversine) and reported in both km and miles. (NOAA's API has no native coordinate search; this tool maintains a cached station directory.)
noaa_get_current_predictions
Get predicted tidal currents for a NOAA current prediction station. interval="max_slack" (recommended for navigation) returns the tidal-current events — maximum flood, maximum ebb, and slack water times — up to 1 year per request. Other intervals (h, 1, 6, 10, 30, 60 minutes) return a velocity time series — up to 31 days. UNITS WARNING: english = knots; metric = cm/s. vel_type="speed_dir" returns Speed/Direction pairs; "default" returns velocities projected on the flood/ebb axis (Velocity_Major: positive = flood direction, negative = ebb) with meanFloodDir/meanEbbDir. Subordinate (type "S") prediction stations derive from a reference station — see noaa_get_prediction_offsets.
noaa_get_currents
Get observed current speed and direction from a NOAA current meter station. Current stations use alphanumeric IDs (e.g. "cb0102" Chesapeake, "bh0101" Boston Harbor) — NOT the 7-digit water-level station IDs. Find them with noaa_search_stations (type "currents") or noaa_find_nearest_stations. UNITS WARNING: english = knots, but metric = cm/s (centimeters/second, not m/s). Returns per record: t (time), s (speed), d (direction, degrees true), b (bin number). Max 7 days per request. Set expand_detailed=true to include per-beam echo intensity and correlation diagnostics.
noaa_get_extreme_water_levels
Get NOAA's extreme water level exceedance statistics for a station: the annual exceedance probability levels (e.g. the 1%-annual-chance "100-year" level) and historical extreme events, computed from the station's verified record. Use for flood risk questions ("what water level has a 1% chance per year at X?"). Levels are relative to the station's datums for the 1983–2001 epoch. Only long-record stations have this product.
noaa_get_harmonic_constituents
Get the harmonic constituents NOAA uses to compute tide or current predictions at a station — the amplitude, phase, and angular speed of each tidal constituent (M2, S2, N2, K1, O1, ...). For water-level stations: amplitude (feet/meters), phase_GMT and phase_local (degrees), speed (degrees/hour). For current stations (alphanumeric IDs) constituents are current ellipses (major/minor amplitudes and phases per depth bin — pass bin to filter). Use for: building custom tide computations, checking a station's dominant constituents (M2 amplitude indicates semidiurnal range), verifying whether a station is harmonically predicted at all. Only reference (R) stations have constituents — subordinate stations use offsets (noaa_get_prediction_offsets).
noaa_get_high_tide_flooding
Get NOAA high tide flooding (HTF, "nuisance"/"sunny day" flooding) statistics for a station. Reports: - daily: flood occurrence per day (REQUIRES start_date and end_date, YYYYMMDD) - monthly / seasonal / annual: counts of minor/moderate/major flood days per period (filter with year/month/season_months, or range = last N periods) - met_year_annual: counts by meteorological year (May–April) - annual_outlook: NOAA's projected flood-day outlook for the coming met year - projections: decadal flood-day projections through 2100 (filter by decade, flood_threshold) - record_days: record flood-day counts - likely_scenarios: likely decadal flooding scenarios - daily_likelihoods: day-by-day flood likelihood forecasts Use for: "how often does X flood?", trends in nuisance flooding, future flooding projections. Not all stations have HTF products — check the HTFhistorical flag via noaa_get_station_info.
noaa_get_meteorological_data
Get observed meteorological/oceanographic sensor data from a NOAA station. Products: air_temperature, water_temperature, wind (speed/gust/direction), air_pressure, air_gap (bridge clearance to water surface), conductivity, visibility, humidity, salinity. Units by system: temps °F/°C; wind knots (english) or m/s (metric); air_gap feet/meters; visibility nautical miles/kilometers; air_pressure always millibars; salinity always PSU. Max span ~31 days per request; interval "6" (6-minute, default) or "h" (hourly). Not every station has every sensor — check with noaa_get_station_info (expand ["sensors"]). Water-level data is served by noaa_get_water_levels, not this tool.
noaa_get_prediction_offsets
Get the offsets a subordinate (type "S") prediction station applies to its reference station's predictions. kind "tide": returns refStationId, time offsets for high/low tide (minutes), height offsets for high/low tide, and whether the height adjustment is a ratio (multiplied) or fixed value — this is how NOAA derives subordinate-station tide times from the reference harmonic station. kind "current": returns refStationId/bin, mean flood/ebb directions, and time adjustments (minutes) for max flood, slack-before-ebb, max ebb, slack-before-flood plus amplitude ratios. Note: current prediction offsets are indexed per bin — pass the station_bin_suffix ID form (e.g. "ACT0091_1") if the plain ID returns nothing. Reference (R) stations return empty/null offsets — they don't need any.
noaa_get_reference_guide
Get curated reference documentation for NOAA CO-OPS concepts and parameters. Topics: - products: Every NOAA CO-OPS data product and which tool serves it - datums: Vertical datums (MLLW, MSL, IGLD...) and station applicability - units: What english vs metric means per measurement (incl. cm/s currents) - time_zones: gmt / lst / lst_ldt semantics and restrictions - intervals: Valid interval values per product family - station_types: Station type filters and station ID formats - data_limits: Maximum date-range span per product - quality_flags: Data quality fields (v/s/f/q), flag letters, HH/H/L/LL - date_formats: Accepted date formats and parameter combinations - marine_forecast: NWS wind & marine forecast tools vs CO-OPS observations Consult this before constructing unusual requests — especially "datums" (which vertical reference to use and station applicability), "units" (english/metric asymmetries like cm/s current speeds), and "data_limits" (maximum date spans per product).
noaa_get_sea_level_rise_projections
Get NOAA's Interagency Sea Level Rise Scenario projections for a station (from the 2022 technical report): projected relative sea level (meters or feet, see units field) per decade through 2150 under the chosen scenario. Scenarios: low, intermediate-low, intermediate, intermediate-high, high, extreme, or all. Use for coastal planning questions ("how much sea level rise is projected at X by 2050?"). Pair with noaa_get_sea_level_trends (observed) and noaa_get_high_tide_flooding (flooding impact).
noaa_get_sea_level_trends
Get the long-term relative sea level trend at a NOAA station: trend and error (reported by NOAA in mm/yr or inches/decade — the payload's trendUnits field says which), the observation period (startDate/endDate), and seasonal amplitude. Relative sea level combines ocean rise AND local land movement (subsidence/uplift), so trends vary widely by station (e.g. strongly positive on the Gulf Coast, negative in Alaska). Requires a station with a long water-level record; omit station to list all (affil "US" or "Global" filters the network).
noaa_get_station_datums
Get the accepted tidal datum values for a station: the elevations of MHHW, MHW, MTL, MSL, DTL, MLW, MLLW, STND, NAVD88 (where computed), plus GT (great diurnal range), MN (mean range), LAT/HAT (lowest/highest astronomical tide), and the station's historical extreme min/max water levels with dates. epoch "current" returns the present National Tidal Datum Epoch (1983–2001) values; "superseded" returns the prior epoch's values (useful for historical comparisons — not all stations have one). All values share one reference zero (the station datum), so datum-to-datum conversion is subtraction: height_above_MLLW = height_above_MSL + (MSL − MLLW). Use this tool to (1) check which datums a station supports before requesting data, and (2) convert heights between datums.
noaa_get_station_info
Get a NOAA station's full metadata record: location, state, time zone, tide type, Great Lakes flag, capability flags, and links to available sub-resources. Optionally expand sub-resources inline via the "expand" list: - details (established/removed dates), sensors (installed instruments + elevations), floodlevels (NOS/NWS minor/moderate/major flood thresholds), benchmarks, products (available data page links), notices, disclaimers — for water-level stations - bins (ADCP depth bins), deployments — for current stations (alphanumeric IDs) Use this before requesting data to confirm what the station actually collects. For datum values use noaa_get_station_datums; for harmonic constituents use noaa_get_harmonic_constituents.
noaa_get_tide_predictions
Get NOAA harmonic tide predictions (future or past) for a station. interval="hilo" (recommended for "when is high/low tide") returns the daily tide events with type H/L — up to 10 years per request. Other intervals (h, 1, 5, 6, 10, 15, 30, 60 minutes) return a height time series — up to 1 year per request. Heights are relative to the requested datum (MLLW default). Notes: - Great Lakes stations have NO tide predictions (lake levels are not tidal). - Subordinate stations (type "S") only support interval=hilo; use the station's reference (R) station for interval series. - Predictions are astronomical only — they exclude weather effects (storm surge, wind setup). Compare with noaa_get_water_levels for actual conditions.
noaa_get_top_ten_water_levels
Get a station's highest recorded water levels: analysis "toptenwaterlevels" returns the ten highest events on record (with date, height, causal event name like "Great New England Hurricane", and category); "peakwaterlevels" returns peak event records (optionally filtered by year). Heights are relative to the requested datum (MHHW is typical for flood comparisons). Use for "what's the worst flooding ever recorded at X?".
noaa_get_water_level_summaries
Get verified summary water-level products from a NOAA station: - high_low: each day's observed highs/lows with ty = HH (higher high), H, L, LL (lower low). Max 1 year per request. - daily_mean: daily mean levels — GREAT LAKES STATIONS ONLY; NOAA requires local standard time, which this tool applies automatically. Max 10 years. - daily_max_min: daily maxima/minima from hourly and 6-minute data with completeness percentages. Max 10 years. - monthly_mean: monthly tidal datum means (columns MHHW, MHW, MSL, MTL, MLW, MLLW, DTL, GT, MN, DHQ, DLQ, HWI, LWI, highest, lowest). Max 200 years — ideal for long-term climatology. Use for: historical extremes, mixed-tide analysis (HH vs H), long-term averages. For raw time series use noaa_get_water_levels; for future tides use noaa_get_tide_predictions.
noaa_get_water_levels
Get observed water levels from a NOAA tide station as a time series. Choose the interval: "6" = standard 6-minute observations (preliminary or verified, max 31 days per request), "1" = 1-minute preliminary data (max 4 days), "hourly" = verified hourly heights (max 1 year). Heights are relative to the requested datum (MLLW by default — the US nautical chart zero). Returns per record: t (timestamp in requested time zone), v (height), s (sigma), f (quality flags, decoded in output), q (p=preliminary, v=verified). Recent data is preliminary; verification takes days to weeks. Use for: "what is the water level right now" (date=latest), storm surge analysis, comparing observed vs predicted tide. Do NOT use for future tides — use noaa_get_tide_predictions.
noaa_search_stations
Search the NOAA CO-OPS station directory by capability type, name, and/or state. Filter with: - type: what the station does (waterlevels, tidepredictions, currents, currentpredictions, met, ...) — pick the type matching the data you plan to request. - name: case-insensitive substring ("San Francisco", "Boston"). - state: two-letter code ("CA", "MA"). Returns id, name, location, tide type, Great Lakes flag, and for prediction stations whether they are reference (R, harmonic) or subordinate (S, offset-based — hilo predictions only). Results are paginated (limit/offset). For proximity search by coordinates use noaa_find_nearest_stations instead.
astro
astro_get_moon_phase
Get the moon phase for a date (or each day of a date range if end_date is given): phase name (New Moon, Waxing Crescent, ...), illuminated fraction, age in days within the 29.53-day cycle, distance (km), apparent diameter (degrees), and waxing/waning. Tide context: spring tides (largest range) occur just after new and full moons; neap tides after quarter moons. Computed locally — no NOAA data involved.
astro_get_next_moon_phase
Find the date(s) of the next occurrence(s) of a principal moon phase (New Moon, First Quarter, Full Moon, Last Quarter) from a starting date. Use for: "when is the next full moon?", planning around spring tides (which follow new/full moons by 1–2 days).
astro_get_next_sun_event
Find the next occurrence(s) of a sun event (sunrise, sunset, dawn, dusk, solarNoon, night, nightEnd, goldenHourStart, goldenHourEnd, nauticalDawn, nauticalDusk, astronomicalDawn, astronomicalDusk) at a location from a starting date. Use for: "when is sunset today?", planning golden-hour photography or dawn fishing around tide windows.
astro_get_sun_position
Get the sun's position for a date, time, and location: azimuth (degrees clockwise from north as rendered here), altitude above the horizon (degrees), plus approximate declination and right ascension. Use for: shadow/lighting analysis, solar exposure. Computed locally with suncalc; declination/RA are approximate.
astro_get_sun_times
Get sunrise, sunset, solar noon, dawn/dusk (civil), nautical dawn/dusk, astronomical dawn/dusk, golden hour, and day length for a location and date (or each day of a range if end_date is given). Times are ISO UTC unless an IANA timezone is provided. At high latitudes some events may be null (e.g. no astronomical night in summer). Computed locally.
nws
nws_get_marine_forecast
Get the official NWS Coastal Waters Forecast (CWF) narrative for the marine zone covering a latitude/longitude — day-part wind/seas text ("SE winds 10 to 15 kt... Bay waters choppy"), including Small Craft Advisories. The point must lie in (or very near) US coastal waters; CWF zones extend roughly 20-60 NM offshore. Returns the zone's segment from the latest bulletin plus the office-wide synopsis. For numeric hourly wind values use nws_get_wind_forecast; for observed wind at a NOAA station use noaa_get_meteorological_data (product "wind").
nws_get_wind_forecast
Get the NWS hourly wind FORECAST (speed, gust, direction — plus wave height where the grid carries it) for a latitude/longitude. Data comes from the NWS forecast grid (api.weather.gov gridpoints — numeric NDFD values, not display strings). Horizon is up to ~7 days (156 hours), starting at the current hour. US and territories only. Wave height appears for marine/nearshore gridpoints; swell/period fields are typically only populated for open-ocean points. Units: english = knots and feet (default), metric = m/s and meters. Direction is degrees true, the direction the wind blows FROM. This is FORECAST data. For observed (measured) wind at a NOAA station right now, use noaa_get_meteorological_data (product "wind"). For the official marine text forecast (Coastal Waters Forecast narrative with small-craft advisories), use nws_get_marine_forecast.
perigee
perigee_whoami
Show how this MCP connection is authenticated: the Perigee account it is linked to (if any), how it signed in (OAuth connector or API key), its rate-limit tier, and the requests-per-minute limit. Use when the user asks which account they're connected as, why they're rate limited, or whether their sign-in worked.

Endpoints

URLTransportStateLatencyChecked
https://perigeetides.com/mcp streamable-http answering 88 ms 9 min ago

NOAA Tides and Currents — questions

Answers built from our own checks of this server.

What can NOAA Tides and Currents do?
It exposes 26 tools, read directly from the server on our last check. Among them: astro_get_moon_phase, astro_get_next_moon_phase, astro_get_next_sun_event, astro_get_sun_position, astro_get_sun_times, noaa_find_nearest_stations and 20 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is NOAA Tides and Currents mostly used for?
Its tools cluster around noaa, astro and nws. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is NOAA Tides and Currents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 535 ms. The bar chart above shows every period we have measured.
The registry lists NOAA Tides and Currents as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect NOAA Tides and Currents?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does NOAA Tides and Currents need an API key?
No. NOAA Tides and Currents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 26 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is NOAA Tides and Currents?
It answers our handshake in 535 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use NOAA Tides and Currents?
The npm package @ryancardin/noaa-tides-currents-mcp-server was installed 114 times in the last week. Week over week that is +46%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is NOAA Tides and Currents open source?
Yes — it is published under the MIT licence, written in TypeScript, 6 stars on GitHub and 4 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.