Tatry Planer
Hiking routes in the Polish and Slovak Tatras: walking times, trail closures, route planning
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://mcp.tatry-planer.workers.dev/mcp | registry |
|---|---|---|
| Handshake | Answers the MCP handshake and lists its tools (266 ms) | our check, 2026-10-26 |
| Protocol version | 2025-11-25 | our check, 2026-10-26 |
| Tools (4) | szukaj_tras, trasa, wyznacz_trase, stan_szlakow | tools/list, 2026-10-26 |
| Registry version | 0.3.0 · active · updated 2026-10-25 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http tatry-planer https://mcp.tatry-planer.workers.dev/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Blitzbuchen Reiseplaner Reisepläne, Last-Minute-Checks und Vergleich eigener Angebote. Keine Livepreise oder…
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/pl.tatry-planer/tatry-planer)<a href="https://openforallofus.com/tools/pl.tatry-planer/tatry-planer"><img src="https://openforallofus.com/badge/pl.tatry-planer/tatry-planer.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name pl.tatry-planer/tatry-planer.