Tides MCP server

by mrfentmen·io.github.mrfentmen/tides-mcp·v1.0.6

No reviews yet

MCP server for NOAA tides and currents predictions and water levels.

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed Tides yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Tides tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

get_tide_predictions
Get NOAA high low or hourly tide predictions for a station and date range.
get_water_levels
Get observed NOAA water levels for a station and short date range.
list_stations
List NOAA tide prediction stations, optionally by state.
station_metadata
Station details for one NOAA tide gauge.
tide_range
Highest, lowest and total tide range for a date window.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan8 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 85 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Tides compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 5; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 5 read

Release history: 2 versions in the registry since 2026-09-21, latest 2026-10-28, typically one every 36 days.

Install Tides in Claude Code, Cursor or VS Code

Runs npx -y tides-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add tides-mcp -- npx -y tides-mcp

Add to Cursor

What the publisher says

From the Tides repository's README, as published. We do not edit it. Read it on GitHub

tides-mcp

A small MCP server for coastal planning with NOAA CO-OPS tide data. It is useful for fishing, kayaking, tidepool trips, photography, flood awareness, and checking whether a tide window is worth investigating.

Tools

gettidepredictions: high and low predictions or hourly predictions for a station and date range.
getwaterlevels: observed water levels for a station and date range.

The server uses the public NOAA CO-OPS API and needs no key. Dates use YYYY-MM-DD; station ids are NOAA station identifiers such as 9414290. Requests time out after 20 seconds.

Run

npm install
npm run build
node dist/index.js

The server uses stdio MCP transport and does not write files or contact any service other than NOAA.

Nothing above is checked by us. What we check is on the safety report.

Tides: common questions

Is Tides MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Tides safety report
How do I install Tides?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Tides need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Tides maintained?: The last commit was 87 days ago (2026-08-08). The latest release is v1.0.6.
How does Tides compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.