Fleet Route Optimizer MCP server
com.kindoflost.routing/fleet-route-optimizerrouting.kindoflost.comstreamable-httpv1.0.0Scanned
Splits deliveries across vehicles and orders each route: time windows, capacities, road times. Free.
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Fleet Route Optimizer MCP server can do
The Fleet Route Optimizer MCP server is published by routing.kindoflost.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: optimize_routes and check_request), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (optimize_routes).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
check_requestSay in plain words what the user wants (e.g.1 finding
Why it is in this group
- The name "check_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "check_request" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check if a routing request fits
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
optimize_routesPlan 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 …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Optimize delivery routes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_route_exampleReturn the full input of one example, in exactly the shape optimize_routes accepts.No findings
Why it is in this group
- The name "get_route_example" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get an example routing input
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_route_resultFetch the result of an optimize_routes job that returned status 'running'.No findings
Why it is in this group
- The name "get_route_result" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a route result
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_route_examplesList the built-in example routing problems.No findings
Why it is in this group
- The name "list_route_examples" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List example routing problems
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://routing.kindoflost.com/mcp: tools/list returned 5 tools to an anonymous client, including optimize_routes (write), check_request (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 1 to 2
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_request
The server marks "check_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "check_request" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:optimize_routesChanges thingsdescriptioninputSchema
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:check_requestChanges things
- Changed:optimize_routesChanges thingsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
- Tools that change things, listed without credentials: 1 to 2
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fleet-route-optimizer https://routing.kindoflost.com/mcpclaude mcp add --transport http fleet-route-optimizer https://routing.kindoflost.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fleet-route-optimizer__list_route_examples",
"mcp__fleet-route-optimizer__get_route_example",
"mcp__fleet-route-optimizer__get_route_result"
],
"ask": [
"mcp__fleet-route-optimizer__optimize_routes",
"mcp__fleet-route-optimizer__check_request"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fleet-route-optimizer. Review it before you use it.
Capability tags behind 1 rule
- mcp__fleet-route-optimizer__optimize_routes untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.kindoflost.routing/fleet-route-optimizer/verify?hash=1b9c9cae06f60badf1a479b2cebec21e068030b3a808090c0c30001b47a1fe0d" | jq -e '.changed == false'Pinned hash 1b9c9cae06f6, from Nov 13, 2026, 15:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.kindoflost.routing/fleet-route-optimizer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.kindoflost.routing/fleet-route-optimizer)Source: MCP Registry. Synced Oct 21, 2026, 17:57 UTC.
Fleet Route Optimizer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fleet Route Optimizer MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Fleet Route Optimizer MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Fleet Route Optimizer MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Fleet Route Optimizer MCP server have?
- 5 tools: 2 write, 3 read. optimize_routes, check_request, list_route_examples, get_route_example and get_route_result.
Does the Fleet Route Optimizer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Fleet Route Optimizer MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Fleet Route Optimizer MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.