Remote MCP · Endpoint

Raute Route Planner MCP server

No. Raute Route Planner answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.raute.io/api/mcp/mcp/

The last check completed an MCP handshake.

Registry name
io.raute/route-planner
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plans delivery routes for up to 25 US addresses and 5 drivers, with the stop order and a map.
Listing
From the official MCP registry (active).
Recent checks of Raute Route Planner
CheckedResultHandshake
1 hour agoHandshake completed73 ms
8 days agoHandshake completed432 ms
9 days agoHandshake completed112 ms
11 days agoHandshake completed125 ms
12 days agoHandshake completed457 ms
13 days agoHandshake completed151 ms
14 days agoHandshake completed74 ms
14 days agoHandshake completed83 ms
16 days agoHandshake completed205 ms
19 days agoHandshake completed116 ms
21 days agoHandshake completed119 ms
24 days agoHandshake completed102 ms
26 days agoHandshake completed64 ms
28 days agoHandshake completed112 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 Raute Route Planner and makes no claim about it beyond what these checks measured.