mcp-registry/app.openkrill/lane-planner · v1.0.1
As of 2026-10-24 00:26 UTC, the Openkrill Lane Planner MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 4 minutes.
Turn a list of interests into a day-by-day plan for 3 to 7 days, with checkbox text for a todo app.
Claude Code
claude mcp add --transport http openkrill-lane-planner-mcp-server https://lanes.openkrill.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"openkrill-lane-planner-mcp-server": {
"type": "http",
"url": "https://lanes.openkrill.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: review_week, ~1,285).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~685 tokens every session. How to fix →
In the last 30 days: 1 tool(s) removed and 5 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.openkrill/lane-planner"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.openkrill/lane-planner"}) over MCP.
review_week ~1,285 tokensplan_lanes ~1,014 tokenssubmit_feedback ~422 tokensindex_tools ~218 tokensget_feedback_reply ~138 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.openkrill%2Flane-planner?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.openkrill%2Flane-planner?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.openkrill%2Flane-planner.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.openkrill%2Flane-planner.svg :target: https://glimind.com/server/mcp-registry%2Fapp.openkrill%2Flane-planner?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:74b950ad74479276…, first seen 2026-10-22, included at leaf 44878 of 55,462. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable search servers · most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-24 00:26 UTC, the Openkrill Lane Planner MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 4 minutes.
Openkrill Lane Planner MCP server advertises 5 tools, including get_feedback_reply, index_tools, plan_lanes, review_week, submit_feedback.
Point your MCP client at this streamable-http endpoint: https://lanes.openkrill.app/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.