Skip to content

OptimoRoute MCP by usefulapi

io.usefulapi/optimorouteusefulapi.iostreamable-httpv1.40.4Scanned

Check OptimoRoute routes, orders and driver events, and create orders or start route planning.

15 tools: 7 can delete or cancel things and 8 only read.

Tools: 7 delete, 0 irreversible, 0 write, 8 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the OptimoRoute MCP by usefulapi can do

The OptimoRoute MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (7 tools: optimoroute_create_order, optimoroute_create_or_update_orders, optimoroute_start_planning, optimoroute_stop_planning and 3 more). 8 tools only read.

2 tools read private data (optimoroute_get_orders and optimoroute_get_completion_details); 1 tool brings in text other people can write (optimoroute_get_completion_details); 1 tool can send data out of your system (optimoroute_send_routes). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

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.

15 tools

Deletes or cancels 7Claude Code: deny
  • optimoroute_create_or_update_ordersCreate, update or replace up to 500 orders in one call.No findings

    Why it is in this group

    • The name "optimoroute_create_or_update_orders" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create, update or replace up to 500 orders in one call. No geocoding here: each location must be an existing locationNo or carry latitude+longitude (+ locationNo, address or locationName). Per order, operation MERGE/SYNC/CREATE/UPDATE works as in optimoroute_create_order; by default an order matched by id or orderNo is updated with only the fields sent, otherwise created. Returns a per-order success list. OptimoRoute: POST /create_or_update_orders.

    Annotations the server declares

    • title: Create or update orders in bulk
    • destructiveHint: true
  • optimoroute_create_orderCreate one order, or update an existing one, with address geocoding.No findings

    Why it is in this group

    • The name "optimoroute_create_order" says "create": a word for a change.
    • The input addresses people (input.allowedDates.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create one order, or update an existing one, with address geocoding. operation: CREATE (new; errors if orderNo exists), UPDATE (existing only), MERGE (create or update only the fields you send — safest for edits), SYNC (create or REPLACE all fields with what you send). CREATE/SYNC/MERGE of a new order need date, type, location and orderNo or id. A location is either an existing locationNo alone, an address to geocode, or latitude+longitude+locationName. OptimoRoute: POST /create_order.

    Annotations the server declares

    • title: Create or update an order
    • destructiveHint: true
  • optimoroute_send_routesDispatch the routes for a date to the drivers' mobile app (the web app's Send Routes).Can send data outNo findings

    Why it is in this group

    • The name "optimoroute_send_routes" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "optimoroute_send_routes" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Dispatch the routes for a date to the drivers' mobile app (the web app's Send Routes). This makes that date the live routes and CANNOT be unsent. sendNotifications defaults to FALSE here (OptimoRoute's own default is true); set it true only when you mean to email/SMS customers per the account's Order Tracking settings. Returns ERR_NOTHING_TO_SEND if nothing changed since the last send. Confirm with optimoroute_get_dispatch_status. OptimoRoute: POST /send_routes.

    Annotations the server declares

    • title: Send routes to drivers
    • destructiveHint: true
  • optimoroute_start_planningStart OptimoRoute's route optimization for a date (or a dateRange for weekly planning, if the plan allows).No findings

    Why it is in this group

    • The name "optimoroute_start_planning" says "start": a word for a change.
    • The input addresses people (input.dateRange.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Start OptimoRoute's route optimization for a date (or a dateRange for weekly planning, if the plan allows). With the default startWith EMPTY, existing routes for that date are REPLACED; use startWith CURRENT (+ lockType) to keep them. Returns a planningId — poll it with optimoroute_get_planning_status, then read the result with optimoroute_get_routes. Can be cancelled with optimoroute_stop_planning. OptimoRoute: POST /start_planning.

    Annotations the server declares

    • title: Start route planning
    • destructiveHint: true
  • optimoroute_stop_planningStop a running planning (optimization) process by its planningId.No findings

    Why it is in this group

    • The name "optimoroute_stop_planning" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Stop a running planning (optimization) process by its planningId. OptimoRoute: POST /stop_planning.

    Annotations the server declares

    • title: Stop route planning
    • destructiveHint: true
  • optimoroute_update_completion_detailsSet the completion status of up to 500 orders (e.g.No findings

    Why it is in this group

    • The name "optimoroute_update_completion_details" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Set the completion status of up to 500 orders (e.g. mark success, failed or cancelled from an external system), optionally with service start/end times. Each time takes unixTimestamp, utcTime or localTime. Reversible by setting the status again. Returns a per-order success list. OptimoRoute: POST /update_completion_details.

    Annotations the server declares

    • title: Update order completion status
    • destructiveHint: true
  • optimoroute_update_driver_parametersChange one driver's setup for one date: enable/disable, work hours, assigned vehicle, vehicle capacities, start/end location.No findings

    Why it is in this group

    • The name "optimoroute_update_driver_parameters" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Change one driver's setup for one date: enable/disable, work hours, assigned vehicle, vehicle capacities, start/end location. WARNING: any existing route for that driver on that date is UNSCHEDULED; re-run planning afterwards. Start/end locations also apply to future optimizations. OptimoRoute: POST /update_driver_parameters.

    Annotations the server declares

    • title: Update a driver's parameters for a date
    • destructiveHint: true
Only reads 8Show 8 read-only tools
  • optimoroute_get_completion_detailsGet the completion status of up to 500 orders (unscheduled, scheduled, on_route, servicing, success, failed, rejected, cancelled) with service start/end times and positions, proof-…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "optimoroute_get_completion_details" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get the completion status of up to 500 orders (unscheduled, scheduled, on_route, servicing, success, failed, rejected, cancelled) with service start/end times and positions, proof-of-delivery form data (notes, signature and photo URLs, barcodes), the tracking URL and optionally customer feedback. Read-only despite using POST. OptimoRoute: POST /get_completion_details.

    Annotations the server declares

    • title: Get order completion details
    • readOnlyHint: true
  • optimoroute_get_dispatch_statusHave the routes (and customer notifications) for a date been sent to drivers, when, and are they the live routes?No findings

    Why it is in this group

    • The name "optimoroute_get_dispatch_status" says "get": a word for reading.
    Description, as the server wrote it
    Have the routes (and customer notifications) for a date been sent to drivers, when, and are they the live routes? Optionally counts routes added, modified or removed since sending. Omit date for the currently live date. OptimoRoute: GET /get_dispatch_status.

    Annotations the server declares

    • title: Get dispatch status
    • readOnlyHint: true
  • optimoroute_get_eventsRead driver-app events for the live routes — on_duty, off_duty, start_route, end_route, start_service, success, failed, rejected, start_time_changed — up to 500 per call.No findings

    Why it is in this group

    • The name "optimoroute_get_events" says "get": a word for reading.
    Description, as the server wrote it
    Read driver-app events for the live routes — on_duty, off_duty, start_route, end_route, start_service, success, failed, rejected, start_time_changed — up to 500 per call. Pass the returned tag as after_tag next time to get only newer events; remainingEvents says whether more are waiting. Events can arrive out of order when devices were offline. OptimoRoute: GET /get_events.

    Annotations the server declares

    • title: Get mobile events
    • readOnlyHint: true
  • optimoroute_get_ordersFetch full order data (location, time windows, assignment, loads, skills, contact) for up to 500 orders by orderNo or id.Reads private dataNo findings

    Why it is in this group

    • The name "optimoroute_get_orders" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    Description, as the server wrote it
    Fetch full order data (location, time windows, assignment, loads, skills, contact) for up to 500 orders by orderNo or id. Each result has its own success flag; missing orders come back with ERR_ORD_NOT_FOUND rather than failing the call. Read-only despite using POST. OptimoRoute: POST /get_orders.

    Annotations the server declares

    • title: Get orders
    • readOnlyHint: true
  • optimoroute_get_planning_statusCheck a planning (route optimization) run started with optimoroute_start_planning: status N new, R running, C cancelled, F finished, E error, plus percentageComplete.No findings

    Why it is in this group

    • The name "optimoroute_get_planning_status" says "get": a word for reading.
    Description, as the server wrote it
    Check a planning (route optimization) run started with optimoroute_start_planning: status N new, R running, C cancelled, F finished, E error, plus percentageComplete. OptimoRoute: GET /get_planning_status.

    Annotations the server declares

    • title: Get planning status
    • readOnlyHint: true
  • optimoroute_get_routesGet the planned routes for one date: per driver/vehicle the duration, distance, loads and the ordered list of stops with scheduled times.No findings

    Why it is in this group

    • The name "optimoroute_get_routes" says "get": a word for reading.
    Description, as the server wrote it
    Get the planned routes for one date: per driver/vehicle the duration, distance, loads and the ordered list of stops with scheduled times. Optionally filter to one driver or vehicle and include the encoded polyline, start/end locations and dispatch status. OptimoRoute: GET /get_routes.

    Annotations the server declares

    • title: Get routes for a date
    • readOnlyHint: true
  • optimoroute_get_scheduling_infoIs this order scheduled, and if so on which driver/vehicle, at which stop number and time, plus the live ETA from the routes sent to drivers.No findings

    Why it is in this group

    • The name "optimoroute_get_scheduling_info" says "get": a word for reading.
    Description, as the server wrote it
    Is this order scheduled, and if so on which driver/vehicle, at which stop number and time, plus the live ETA from the routes sent to drivers. Give orderNo or id. OptimoRoute: GET /get_scheduling_info.

    Annotations the server declares

    • title: Get an order's scheduling info
    • readOnlyHint: true
  • optimoroute_search_ordersFind orders in a date range (at most 35 days) or by a list of orderNo/id, optionally filtered by status (e.g.No findings

    Why it is in this group

    • The name "optimoroute_search_orders" says "search": a word for reading.
    Description, as the server wrote it
    Find orders in a date range (at most 35 days) or by a list of orderNo/id, optionally filtered by status (e.g. failed, rejected, unscheduled), with order data and/or scheduling info. Up to 500 per page; pass the returned after_tag with the SAME other parameters to get the next page. Read-only despite using POST. OptimoRoute: POST /search_orders.

    Annotations the server declares

    • title: Search orders
    • readOnlyHint: true

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.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
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 out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__optimoroute__optimoroute_send_routes"
    ]
  }
}

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.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://optimoroute.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://optimoroute.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://optimoroute.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://optimoroute.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http optimoroute https://optimoroute.usefulapi.io/mcp
claude mcp add --transport http optimoroute https://optimoroute.usefulapi.io/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__optimoroute__optimoroute_get_routes",
      "mcp__optimoroute__optimoroute_get_orders",
      "mcp__optimoroute__optimoroute_search_orders",
      "mcp__optimoroute__optimoroute_get_scheduling_info",
      "mcp__optimoroute__optimoroute_get_completion_details",
      "mcp__optimoroute__optimoroute_get_events",
      "mcp__optimoroute__optimoroute_get_planning_status",
      "mcp__optimoroute__optimoroute_get_dispatch_status"
    ],
    "ask": [],
    "deny": [
      "mcp__optimoroute__optimoroute_create_order",
      "mcp__optimoroute__optimoroute_create_or_update_orders",
      "mcp__optimoroute__optimoroute_start_planning",
      "mcp__optimoroute__optimoroute_stop_planning",
      "mcp__optimoroute__optimoroute_update_driver_parameters",
      "mcp__optimoroute__optimoroute_update_completion_details",
      "mcp__optimoroute__optimoroute_send_routes"
    ]
  }
}

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 optimoroute. Review it before you use it.

Capability tags behind 3 rules
  • mcp__optimoroute__optimoroute_get_orders private-data
  • mcp__optimoroute__optimoroute_get_completion_details private-data, untrusted-input
  • mcp__optimoroute__optimoroute_send_routes outbound

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/io.usefulapi/optimoroute/verify?hash=abe51e7d63a28d72cdda6f72c1a2b21aa3769a564622fd29373fe20de8683f7d" | jq -e '.changed == false'

Pinned hash abe51e7d63a2, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/optimoroute/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/optimoroute
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/optimoroute.svg)](https://radar.anlyon.com/servers/io.usefulapi/optimoroute)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

OptimoRoute MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OptimoRoute MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the OptimoRoute MCP by usefulapi delete data?

Yes. 7 tools can delete, cancel or revoke something: optimoroute_create_order, optimoroute_create_or_update_orders, optimoroute_start_planning, optimoroute_stop_planning, optimoroute_update_driver_parameters, optimoroute_update_completion_details and 1 more.

Can the OptimoRoute MCP by usefulapi 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 OptimoRoute MCP by usefulapi have?

15 tools: 7 destructive, 8 read. optimoroute_create_order, optimoroute_create_or_update_orders, optimoroute_start_planning, optimoroute_stop_planning, optimoroute_update_driver_parameters, optimoroute_update_completion_details, optimoroute_send_routes, optimoroute_get_routes and 7 more.

Does the OptimoRoute MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the OptimoRoute MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): optimoroute_send_routes.

Has the OptimoRoute MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.