Remote MCP · Endpoint
NOAA Tides and Currents MCP server
No. NOAA Tides and Currents answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://perigeetides.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.RyanCardin15/noaa-tides-and-currents-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 361 ms
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- NOAA tides and currents: water levels, tide predictions, currents, met data, flooding, sun and moon
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 361 ms |
| 2 days ago | Handshake completed | 296 ms |
| 4 days ago | Handshake completed | 1.94 s |
| 6 days ago | Handshake completed | 665 ms |
| 7 days ago | Handshake completed | 257 ms |
| 9 days ago | Handshake completed | 295 ms |
| 10 days ago | Handshake completed | 409 ms |
| 11 days ago | Handshake completed | 289 ms |
| 14 days ago | Handshake completed | 306 ms |
| 15 days ago | Handshake completed | 300 ms |
| 17 days ago | Handshake completed | 351 ms |
| 18 days ago | Handshake completed | 315 ms |
| 19 days ago | Handshake completed | 277 ms |
| 20 days ago | Handshake completed | 243 ms |
| 21 days ago | Handshake completed | 300 ms |
| 22 days ago | Handshake completed | 196 ms |
| 23 days ago | Handshake completed | 303 ms |
| 24 days ago | Handshake completed | 307 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with NOAA Tides and Currents and makes no claim about it beyond what these checks measured.