Fleet Route Optimizer
REMOTE · ROUTING.KINDOFLOST.COM
Splits deliveries across vehicles and orders each route: time windows, capacities, road times. Free.
Available components
Last scanned (1 day ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1181 tokens (~236/item across 5 items; 5 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 Management88
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 12 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “optimize_routes” rewrote its description, which is the text the model reads security
- 6 Nov 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “optimize_routes” rewrote its description, which is the text the model reads security
- Schema quality: 865 → 1079 ▼ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “plan_deliveries_time_windows” functional
- New prompt “plan_routes_from_addresses” functional
- New prompt “planificar_rutas_reparto” functional
- Server version: 1.0.0 → 1.0.1 functional
- New tool “check_request” functional
- “optimize_routes” added an optional parameter “goal” cosmetic
- “optimize_routes” reworded the description of “depot” cosmetic
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Sept 26 0
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 21 Nov 2026 · Probed https://routing.kindoflost.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=routing.kindoflost.com | CN=WE1,O=Google Trust Services,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 839d0fb0073ea50c1369fa00375d3b53 |
| SANs: routing.kindoflost.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of routing.kindoflost.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| kindoflost.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://routing.kindoflost.com/mcp | Verified | 200 | |
| http (plaintext) | http://routing.kindoflost.com/mcp | HTTPS enforced | 301 | https://routing.kindoflost.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_request Check if a routing request fits ~84
Say in plain words what the user wants (e.g. 'two depots, 40 pickups and deliveries, 3 vans'). Returns whether this server can do it and, if not, the closest thing it can do. Fast, no solve. Call it first when unsure the tool fits.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | The user's routing problem in a sentence or two. |
No output schema declared.
No examples provided.
get_route_example Get an example routing input ~61
Return the full input of one example, in exactly the shape optimize_routes accepts. Edit it (depot, stops, vehicles, windows) to match the user's situation.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | es = Spanish labels. |
| name | string | yes | – |
No output schema declared.
No examples provided.
get_route_result Get a route result ~63
Fetch the result of an optimize_routes job that returned status 'running'. Waits up to wait_seconds; call again while status is 'running'. Jobs expire 15 minutes after they finish.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
list_route_examples List example routing problems ~37
List the built-in example routing problems. Use one to see a realistic input, or solve it as-is to show what the tool does.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
optimize_routes Optimize delivery routes ~670
Plan routes for one or more vehicles from one depot and return, per vehicle, the stop order with arrival times and load so far, plus stops that could not be served, totals, Google Maps links, a driver_link per route (a phone page with tap-to-navigate for every stop, nothing stored) and warnings. Uses real road driving times. Solves take 10-60 s (more when many addresses must be looked up). Pass either `example` or the fields below. If the result has status 'running', call get_route_result with its job_id. Minimal example: {"depot": {"address": "1600 Pennsylvania Ave NW, Washington, DC 20500"}, "stops": [{"id": "Ana", "address": "..."}, {"id": "Bob", "lat": 38.9, "lon": -77.03, "window_open": "09:00", "window_close": "12:00", "service_minutes": 10}], "vehicles": 2}. Omitted: capacity = unlimited, no time windows, 1 vehicle, depot = the first stop, stops are dropped only when they cannot be served at all; every default applied is listed in the result's 'assumptions'. Call get_route_example for complete, realistic inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Which geocoder reads the addresses: US (US Census, then OpenStreetMap) or OTHER (OpenStreetMap). Default US. |
| depot | object|string | – | REQUIRED in practice: where every vehicle starts and ends, as an OBJECT with an address or lat+lon (a plain address string is also accepted and used as the address), e.g. {"address": "1 Main St, Spri… |
| example | string | – | Solve this built-in example instead of passing the fields below. |
| goal | string | – | One sentence, in the user's own words, of what they are trying to do (e.g. 'plan tomorrow's deliveries for 3 vans'). Optional; helps improve the tool. |
| parameters | object | – | Optional engine settings: SearchParametersTimeLimit (seconds, default 30, max 60), NoImprovementSeconds (20), RouteTimeLimit (minutes, default 1440), DroppedOrderCost (100000 = serve every stop that… |
| previous_routes | array | – | Re-optimize from existing routes: one list of stop ids (or 1-based stop numbers) per vehicle, in visiting order. The solver starts from these and improves them; new stops are fitted in. |
| stops | array | – | The places to visit (not the depot). Each needs an address or lat+lon. |
| vehicles | – | – | Either a number of identical vehicles (unlimited capacity), or one object per vehicle. |
| wait_seconds | integer | – | How long to wait for the solve inside this call (default 25). |
No output schema declared.
No examples provided.
How do I install the Fleet Route Optimizer MCP server?
Fleet Route Optimizer is a hosted endpoint at https://routing.kindoflost.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 · routing.kindoflost.com
claude mcp add --transport http com-kindoflost-routing-fleet-route-optimizer 'https://routing.kindoflost.com/mcp'
What is the Fleet Route Optimizer MCP server?
Fleet Route Optimizer is an MCP server listed in the public MCP registry as com.kindoflost.routing/fleet-route-optimizer. Splits deliveries across vehicles and orders each route: time windows, capacities, road times. Free. This page covers its hosted endpoint (https://routing.kindoflost.com/mcp).
Is the Fleet Route Optimizer MCP server safe to use?
Fleet Route Optimizer scores 85 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 Fleet Route Optimizer MCP server expose?
Fleet Route Optimizer exposes 5 tools: list_route_examples, get_route_example, optimize_routes, check_request, get_route_result. Their descriptions and schemas cost roughly 915 tokens of context every time the server is loaded.
Does the Fleet Route Optimizer MCP server require authentication?
No. We connected to Fleet Route Optimizer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fleet Route Optimizer MCP server still maintained?
Fleet Route Optimizer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Fleet Route Optimizer MCP server?
VerifyMCP ran 13 checks on Fleet Route Optimizer, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.