Back to MCP servers

Find My Tide

https://findmytide.com/mcp
● degraded

Tide predictions for about 4,600 stations in the United States, Canada and US territories. It gives the same predictions as findmytide.com and the Find My Tide apps. - **search_stations**: find stations by place name ("Tofino", "Bay of Fundy") or the nearest to a latitude and longitude. - **get_tides**: high and low tide times and heights for up to seven days in the station's local time, plus the current height and whether the tide is rising or falling. - **get_conditions**: current wind, sea temperature and sky at a station. Free, with no account or API key. All tools are read-only. Data comes from NOAA CO-OPS and the Canadian Hydrographic Service. **Not suitable for navigation.** Every answer carries that notice and its source's attribution.

Transport
streamable-http
Auth
—
Cost
—
Protocol revision
—

MCP readiness

F · 16/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here E, 13.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 0/10 initialize did not answer cleanly (HTTP 405).
Live MCP endpoint 5/25 Endpoint answers, but not with MCP JSON-RPC (497 ms).
Protocol revision 0/10 No protocol revision reported by initialize.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 0/15 0/22 probes succeeded over 30 days (0%).
Tool declaration 0/10 No tools listed by tools/list.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (497 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness
Higher than 0% of peers
This listing 16 · peer median 81
Latency
Faster than 31% of peers
This listing 497 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Live MCP endpoint −20 — Answer initialize and tools/list at the declared endpoint.
    Now: Endpoint answers, but not with MCP JSON-RPC (497 ms).
  • Uptime (30 days) −15 — Stay reachable in our daily probes.
    Now: 0/22 probes succeeded over 30 days (0%).
  • Valid MCP handshake −10 — Complete the MCP handshake without errors.
    Now: initialize did not answer cleanly (HTTP 405).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://findmytide.com/mcp
JSON-RPC initialize probe
curl -X POST https://findmytide.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://findmytide.com
Listed at (agenstry)
https://agenstry.com/mcp/findmytide/tides