Canal Nav
com.canalnav/canal-nav · 1.0.0
Plan canal routes on Great Britain's waterways: lock-aware timing, live closures, boat-fit checks.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.canalnav.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 6 tools.
- Protocol
- 2025-06-18
- Calls itself
- canal-nav 1.0.0
- Handshake time
- 276 ms
- HTTP status
- 200
The tools it lists (6, as of 5 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
plan_routePlan a boat journey between two points on the inland waterways of Great Britain (canals and navigable rivers). The route follows the water itself, not roads. It counts every lock and estimates cruising time from realistic boat speed plus time per lock. Live closures and stoppages from every GB navigation authority (Canal & River Trust, Environment Agency, Scottish Canals, Broads Authority and others) are routed around automatically, and when a dated closure blocks the natural line the result compares waiting for it to reopen against taking the detour. Give boat dimensions to get per-waterway f
plan_round_tripPlan return-to-start cruises from a point on the inland waterways of Great Britain, sized to fit a number of days. Returns several options: circular loops where the canal network offers one (canal "rings"), plus out-and-back and fewest-locks alternatives, each with distance, lock count, day-by-day plan and suggested overnight moorings. Timing is lock-aware and closures from every GB navigation authority are flagged on each option. Give boat dimensions to get fit warnings, and routes touching tidal water carry a tidal safety warning. The start can be a place name or "lat,lon" coordinates.
get_closuresLive closure, stoppage and restriction notices for the inland waterways of Great Britain, covering every GB navigation authority: Canal & River Trust, Environment Agency, Scottish Canals, Broads Authority, Bridgewater, Middle Level, River Wey, Basingstoke and more, not just CRT. Search near a place (name or "lat,lon", with an optional radius) or by waterway name (e.g. "Oxford Canal"). Returns active and upcoming notices with dates, the responsible authority, whether each one blocks navigation, and links for detail. Data refreshes from the authorities' published notices, so reopen dates reflect
will_my_boat_fitCheck boat dimensions against the published maximum craft dimensions for a named British waterway (length, beam, draught and air draught, from Canal & River Trust published figures covering the full CRT network). Returns a per-dimension verdict quoting the limit. Draught and headroom vary with water level and silting, so treat the answer as advisory. For a whole journey, use plan_route with boat dimensions instead: it checks every waterway along the route.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.canalnav/canal-nav, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 70 days ago. The registry entry · canalnav.com