Remote MCP · Endpoint

Lane Planner MCP server

No. Lane Planner answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://lanes.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/lane-planner
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
324 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Turn a list of interests into a day-by-day plan for 3 to 7 days, with checkbox text for a todo app.
Listing
From the official MCP registry (active).
Recent checks of Lane Planner
CheckedResultHandshake
3 hours agoHandshake completed324 ms
13 hours agoHandshake completed341 ms
2 days agoHandshake completed551 ms
4 days agoHandshake completed374 ms
7 days agoHandshake completed308 ms
9 days agoHandshake completed226 ms
11 days agoHandshake completed308 ms
14 days agoHandshake completed171 ms
15 days agoHandshake completed549 ms
18 days agoHandshake completed434 ms
20 days agoHandshake completed668 ms
21 days agoHandshake completed66 ms
23 days agoHandshake completed1.17 s

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

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