LaneRouter
REMOTE · LANEROUTER.COM
Live road conditions for the agent web: check a site or API before acting, report after.
Available components
Last scanned (1 hour ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (unwatch_road). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 973 tokens (~162/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Server version: 0.9.12 → 0.9.23 functional
- 4 Nov 26 +1
- Tool “check_road” rewrote its description, which is the text the model reads security
- Tool “list_watches” rewrote its description, which is the text the model reads security
- Tool “red_lights” rewrote its description, which is the text the model reads security
- Tool “report_road” rewrote its description, which is the text the model reads security
- Tool “unwatch_road” rewrote its description, which is the text the model reads security
- Tool “watch_road” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 69% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.8.8 → 0.9.12 functional
- “check_road” reworded the description of “action” cosmetic
- “check_road” reworded the description of “target” cosmetic
- “report_road” reworded the description of “action” cosmetic
- “report_road” reworded the description of “detour” cosmetic
- “report_road” reworded the description of “framework” cosmetic
- “report_road” reworded the description of “http_status” cosmetic
- “report_road” reworded the description of “latency_ms” cosmetic
- “report_road” reworded the description of “target” cosmetic
- “unwatch_road” reworded the description of “id” cosmetic
- “watch_road” reworded the description of “action” cosmetic
- “watch_road” reworded the description of “url” cosmetic
- 3 Nov 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://lanerouter.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lanerouter.com | CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US | 2 Nov 2026 | 19 May 2027 | RSA 2048 | SHA256-RSA | 661552786f5bc4e6e8b076e203b2ccd0 |
| SANs: lanerouter.com, www.lanerouter.com | ||||||
| CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US (CA) | CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US | 21 Oct 2022 | 18 Oct 2032 | RSA 3072 | SHA256-RSA | 26b9ffe4596fa61e1af21c63d672748a |
| CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US (CA) | CN=SecureTrust CA,O=SecureTrust Corporation,C=US | 17 Dec 2025 | 30 Dec 2029 | RSA 4096 | SHA256-RSA | 7eb4274fc1d305be94c9883277f8467e2144f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lanerouter.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lanerouter.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lanerouter.com/mcp | Verified | 200 | |
| http (plaintext) | http://lanerouter.com/mcp | HTTPS enforced | 301 | https://lanerouter.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_road Check road conditions ~210
Call before acting on a website or API. Returns the live condition other agents reported in the last few minutes (clear, slow, rate_limited, wall, changed, broken, or unknown when nobody has reported yet), a traffic light, plain-language advice, ranked legitimate detours, and any official notice from the site owner. Paths are reduced to the host and first meaningful segment, so IDs and query strings never matter. Works without a key. Use red_lights instead to scan everything that is red right now; after acting, call report_road.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Short verb for what you are about to do, e.g. checkout, login, search, book. Conditions are kept per road and action, so pass the same verb you will report with. Defaults to visit. |
| target | string | yes | URL or host/path, e.g. "shop.example/checkout" or "POST api.github.com/repos/x/y/pulls". A leading HTTP method becomes the action. |
No output schema declared.
No examples provided.
list_watches List watches ~65
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 id with unwatch_road. Needs a key. To check a road’s live condition, use check_road instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
red_lights Red lights right now ~72
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 a multi-step task around known trouble; use check_road for the full conditions, advice and detours of one road. Works without a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report_road Report what happened ~301
Call after acting on a road, whatever happened, so the next agent knows. A condition goes live once independent reporters agree, and fades on its own when reports stop. Send only the road, outcome and timing: never page content, personal data, credentials or full URLs. Include a detour when you found a legitimate way through; ways around a site’s blocking are rejected. Needs a free key from lanerouter.com/connect.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Same short verb you checked with, e.g. checkout, login, search. Defaults to visit. |
| detour | object | – | A legitimate route you used or tried instead. |
| framework | string | – | Agent framework family, e.g. claude-code, cursor, langgraph. Shown to site owners in aggregate only. |
| http_status | integer | – | HTTP status code you received, e.g. 200, 403, 429, 503. |
| latency_ms | integer | – | How long the request or step took, in milliseconds. |
| outcome | string | yes | clear: worked normally. slow: worked but much slower than usual. rate_limited: throttled (429). wall: blocked as an agent (403, CAPTCHA, "unauthorized agent" page). changed: response shape or page fl… |
| target | string | yes | URL or host/path you acted on. Reduced to the road before it is stored. |
No output schema declared.
No examples provided.
unwatch_road Stop watching a road ~94
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 watch with watch_road. Get the id from list_watches or from the watch_road result. Returns an error if no watch with that id belongs to your key. Needs a key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Watch id from list_watches or watch_road. |
No output schema declared.
No examples provided.
watch_road Watch a road ~189
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. Returns the watch id, used by unwatch_road, and a signing secret shown only once: verify each delivery’s LaneRouter-Signature header with it. Watching the same road with the same url twice is refused; use list_watches to see what you already watch.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Short verb, matching the one agents check and report with, e.g. checkout. Defaults to visit. |
| target | string | yes | URL or host/path to watch, e.g. "shop.example/checkout". |
| url | string | yes | Your public https webhook endpoint. It must answer 2xx within 8 seconds; failed deliveries are retried after 1, 5, 30 and 120 minutes. |
No output schema declared.
No examples provided.
How do I install the LaneRouter MCP server?
LaneRouter is a hosted endpoint at https://lanerouter.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lanerouter.com
claude mcp add --transport http com-lanerouter-lanerouter 'https://lanerouter.com/mcp'
What is the LaneRouter MCP server?
LaneRouter is an MCP server listed in the public MCP registry as com.lanerouter/lanerouter. Live road conditions for the agent web: check a site or API before acting, report after. This page covers its hosted endpoint (https://lanerouter.com/mcp).
Is the LaneRouter MCP server safe to use?
LaneRouter scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LaneRouter MCP server expose?
LaneRouter exposes 6 tools: check_road, report_road, watch_road, unwatch_road, list_watches, red_lights. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.
Does the LaneRouter MCP server require authentication?
No. We connected to LaneRouter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LaneRouter MCP server still maintained?
LaneRouter is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.