Remote MCP · Endpoint
Clairwave MCP server
No. Clairwave answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.clairwave.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.clairwave/clairwave
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 333 ms
- Tools exposed
- 13 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Ocean acoustics: propagation models, bathymetry, sound speed, vessel noise, live AIS. Open.
- Website
- https://www.clairwave.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 333 ms |
| 1 day ago | Handshake completed | 125 ms |
| 2 days ago | Handshake completed | 132 ms |
| 3 days ago | Handshake completed | 183 ms |
| 4 days ago | Handshake completed | 189 ms |
| 5 days ago | Handshake completed | 244 ms |
| 6 days ago | Handshake completed | 199 ms |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Handshake completed | 101 ms |
| 14 days ago | Handshake completed | 346 ms |
| 16 days ago | Handshake completed | 209 ms |
| 18 days ago | Handshake completed | 492 ms |
| 20 days ago | Handshake completed | 625 ms |
| 22 days ago | Handshake completed | 96 ms |
| 24 days ago | Handshake completed | 93 ms |
| 26 days ago | Handshake completed | 149 ms |
| 27 days ago | Handshake completed | 173 ms |
| 29 days ago | Handshake completed | 611 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.
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 Clairwave and makes no claim about it beyond what these checks measured.