Remote MCP · Endpoint
Canal Nav MCP server
No. Canal Nav answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.canalnav.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.canalnav/canal-nav
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 422 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Plan canal routes on Great Britain's waterways: lock-aware timing, live closures, boat-fit checks.
- Website
- https://canalnav.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 422 ms |
| 19 hours ago | Handshake completed | 327 ms |
| 2 days ago | Handshake completed | 293 ms |
| 3 days ago | Handshake completed | 305 ms |
| 4 days ago | Handshake completed | 324 ms |
| 5 days ago | Handshake completed | 411 ms |
| 6 days ago | Handshake completed | 333 ms |
| 8 days ago | Handshake completed | 631 ms |
| 10 days ago | Handshake completed | 285 ms |
| 13 days ago | Handshake completed | 356 ms |
| 15 days ago | Handshake completed | 286 ms |
| 17 days ago | Handshake completed | 302 ms |
| 19 days ago | Handshake completed | 305 ms |
| 21 days ago | Handshake completed | 306 ms |
| 23 days ago | Handshake completed | 277 ms |
| 25 days ago | Handshake completed | 302 ms |
| 27 days ago | Handshake completed | 295 ms |
| 28 days ago | Handshake completed | 349 ms |
| 29 days ago | Handshake completed | 299 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 Canal Nav and makes no claim about it beyond what these checks measured.