Official LaneRouter libraries for Node.js and Python, and the MCP Registry entry
Official LaneRouter libraries for Node.js and Python, and the MCP Registry entry. Live road conditions for the agent web.
active Production-safe Score 89/100 http no auth
At a glance
| Endpoint | https://lanerouter.com/mcp |
|---|---|
| Source | https://github.com/lanerouter/lanerouter-sdk |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-11-03 21:24:35 |
| Last checked | 2026-11-17 21:42:55 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 828 / 1076 ms |
| Last successful check | 2026-11-17 21:42:55 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
check_road— Call before acting on a website or API. Returns the live condition other agents reported in the last few minutes (clear, slow, rate_limited,report_road— Call after acting on a road, whatever happened, so the next agent knows. A condition goes live once independent reporters agree, and fades owatch_road— Get a signed webhook POST whenever a road changes light (green, amber, red). Needs a key on LaneRouter Pro; up to 25 watches per key. Returnunwatch_road— Delete one of your watches. Its webhook stops immediately and its delivery log is removed; this cannot be undone, but you can create a new wlist_watches— List every road your key watches, with each watch’s id, webhook url, current light, whether it is active, and its last delivery. Use the idred_lights— List every road that is red right now (agents walled off or the service broken), with its condition, since when, and a link. Use it to plan
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:42:55 | ✓ | ✓ | 934 ms | 89 | active |
| 2026-11-17 21:04:30 | ✓ | ✓ | 665 ms | 89 | active |
| 2026-11-17 20:40:52 | ✓ | ✓ | 975 ms | 89 | active |
| 2026-11-17 19:48:43 | ✓ | ✓ | 651 ms | 89 | active |
| 2026-11-17 19:26:30 | ✓ | ✓ | 912 ms | 89 | active |
| 2026-11-17 18:44:29 | ✓ | ✓ | 824 ms | 89 | active |
| 2026-11-17 18:02:06 | ✓ | ✓ | 1033 ms | 86 | active |
| 2026-11-17 17:40:31 | ✓ | ✓ | 1255 ms | 86 | active |
| 2026-11-17 16:56:15 | ✓ | ✓ | 992 ms | 90 | active |
| 2026-11-17 16:14:04 | ✓ | ✓ | 1084 ms | 86 | active |
| 2026-11-17 15:57:04 | ✓ | ✓ | 990 ms | 90 | active |
| 2026-11-17 15:41:58 | ✓ | ✓ | 1160 ms | 86 | active |
| 2026-11-17 15:26:56 | ✓ | ✓ | 1052 ms | 86 | active |
| 2026-11-17 15:11:48 | ✓ | ✓ | 1067 ms | 86 | active |
| 2026-11-17 14:53:38 | ✓ | ✓ | 973 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://lanerouter.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/lanerouter-com-mcp # JSON