Upper Route Planner MCP by usefulapi
REMOTE · UPPER-ROUTE-PLANNER.USEFULAPI.IO
Read Upper drivers and stops; create and optimize routes, assign drivers, share routes to the app.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “assign_drivers_optimize_and_wait_for_the_result” functional
- New prompt “find_stops_that_are_not_on_a_route_yet” functional
- New prompt “move_or_correct_a_stop” functional
- New prompt “review_the_stops_of_one_route” functional
- New prompt “send_a_finished_route_to_the_drivers_app” functional
- New prompt “set_up_tomorrow_s_route_from_a_list_of_addresses” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.7.0 → 1.9.0 functional
- Server version: 1.6.0 → 1.7.0 functional
- Server version: 1.5.2 → 1.6.0 functional
- 30 Oct 26 +1
- Server version: 1.5.1 → 1.5.2 functional
- Server version: 1.5.0 → 1.5.1 functional
- 29 Oct 26 0
- Server version: 1.4.0 → 1.5.0 functional
- Server version: 1.3.0 → 1.4.0 functional
- 28 Oct 26 +1
- Server version: 1.1.0 → 1.3.0 functional
- 27 Oct 26 0
- Server version: 1.0.0 → 1.1.0 functional
- 26 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
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 6 Nov 2026 · Probed https://upper-route-planner.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 upper-route-planner.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://upper-route-planner.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/upper-route-planner/ |
| http (plaintext) | http://upper-route-planner.usefulapi.io/mcp | Inconclusive | 302 | http://upper-route-planner.usefulapi.io/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 →
upper_assign_drivers Assign drivers to a route ~103
WRITE: assign one or more drivers (ids from upper_list_drivers) to a route, replacing the route's drivers. Every id must be an active driver on the team. If the route was already optimized it is reset to unoptimized (needs_optimization: true), so run upper_optimize_route again. POST /ext-assign-drivers.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_ids | array | yes | Driver ids to assign. |
| route_id | integer | yes | The route. |
No output schema declared.
No examples provided.
upper_create_route Create route ~168
WRITE: create a new, empty route (name, date, optimization preference, units, pickup sequencing, service time). Omitted settings fall back to the account's defaults. Returns the new route_id; add stops with upper_create_stop. Calling it twice creates two routes. POST /ext-create-route.
| Name | Type | Req | Description |
|---|---|---|---|
| optimize_for | string | – | Optimize for time or distance. |
| pickup_settings | string | – | When pickups are sequenced: auto, before or after the deliveries. |
| route_date | string | – | Route start date, yyyy-mm-dd (default today). |
| route_name | string | – | Route name (default: New Route). |
| service_time | integer | – | Per-stop service (dwell) time in seconds. |
| units | string | – | Distance units: miles or km. |
No output schema declared.
No examples provided.
upper_create_stop Create stop ~474
WRITE: create a stop. The address is geocoded by Upper. Pass route_id to put it on a route (the route must not be active/in progress; an optimized route is flagged for re-optimization); omit it for an unscheduled stop. Calling it twice creates two stops. POST /ext-create-stop.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address of the stop (geocoded by Upper). |
| capacity_fields | object | – | Capacity values (integers) for load planning, keys capacity1 - capacity5. |
| city | string | – | City (overrides the geocoded value). |
| company_name | string | – | Company name for the stop. |
| contact_name | string | – | Contact (recipient) name. |
| custom_fields | object | – | Custom field values keyed by slot (custom1 - custom5). Only fields enabled in the workspace (and in the plan) are stored. |
| customer_system_id | string | – | Your own identifier for the stop (for cross-referencing). |
| string | – | Contact email. | |
| end_time | string | – | Latest service time (time window end), HH:MM or HH:MM:SS. |
| nick_name | string | – | Short label for the stop. |
| note | string | – | Free-text note shown to the driver. |
| parcel_count | integer | – | Number of parcels at the stop. |
| phone | string | – | Contact phone number; non-digits are stripped by Upper. |
| phone_country_code | string | – | Phone dialing code, for example 1. |
| pin_color | string | – | Map pin colour, hex like #FF6600. |
| route_id | integer | – | Route to attach the stop to; omit for an unscheduled stop. |
| start_time | string | – | Earliest service time (time window start), HH:MM or HH:MM:SS. |
| state | string | – | State or region (overrides the geocoded value). |
| stop_duration | integer | – | Service duration at the stop, in seconds. |
| stop_priority | string | – | Stop priority, for example Normal, High, Urgent. |
| stop_type | string | – | Stop type, for example Delivery or Pickup. |
| zipcode | string | – | Postal code (overrides the geocoded value). |
No output schema declared.
No examples provided.
upper_get_capacity_fields Get capacity fields ~43
The workspace's five capacity-field slots (capacity1 - capacity5: label, unit, enabled) used for load planning. GET /ext-get-capacity-fields.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upper_get_custom_fields Get stop custom fields ~55
The workspace's five stop custom-field slots (custom1 - custom5: type, label, enabled, required) and which are enabled. Needs the Custom fields feature in the Upper plan. GET /ext-get-custom-fields.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upper_get_optimization_status Get route optimization status ~67
Check whether a route is optimized: status is optimized, pending (still running) or not_optimized, plus the queue_id of the last job. Poll this after upper_optimize_route. GET /ext-optimization-status.
| Name | Type | Req | Description |
|---|---|---|---|
| route_id | integer | yes | The route id. |
No output schema declared.
No examples provided.
upper_list_drivers List drivers ~55
List the active drivers on the Upper team that owns the API token: id, name, email and phone. Use the ids with upper_assign_drivers and upper_share_route_to_drivers. GET /ext-get-drivers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upper_list_stops List stops ~226
List the team's stops in optimized order: address, coordinates, contact, time window, duration, status, route_id and custom ids. Pass route_id for one route (optionally scheduled=true/false); pass unscheduled=true (without route_id) for stops not on any route; with no filter all active stops are returned. Upper has no paging, so this tool pages locally: `limit` stops (default 100, max 500) starting at `offset`; the reply says if more remain (truncated, next_offset). GET /ext-get-stops.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most stops to return, 1-500 (default 100). |
| offset | integer | – | Skip this many stops (use next_offset from the previous reply to read on). |
| route_id | integer | – | Only the stops on this route. |
| scheduled | boolean | – | With route_id only: true = scheduled stops, false = unscheduled stops of that route. |
| unscheduled | boolean | – | Without route_id: true = unscheduled stops across all routes. |
No output schema declared.
No examples provided.
upper_optimize_route Optimize route ~109
WRITE: start optimizing a route's stop order. The route needs at least one stop and one assigned driver (upper_assign_drivers). It runs asynchronously: this returns status pending and a queue_id, then poll upper_get_optimization_status. If a job is already running, that job is returned. POST /ext-optimize-route.
| Name | Type | Req | Description |
|---|---|---|---|
| route_id | integer | yes | The route to optimize. |
| timezone | string | – | IANA timezone for the optimization, for example America/New_York. |
No output schema declared.
No examples provided.
upper_share_route_to_drivers Share route to drivers ~125
WRITE: push a route to the drivers' mobile app NOW, which sends each driver a notification. Without driver_ids the route's assigned drivers are used; with them, every id must be an active driver on the team. Sending twice notifies twice. Confirm with the user before calling. POST /ext-share-to-driver.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_ids | array | – | Drivers to notify (default: the route's assigned drivers). |
| route_id | integer | yes | The route to share. |
| timezone | string | – | IANA timezone, for example America/New_York. |
No output schema declared.
No examples provided.
upper_update_route Update route ~147
WRITE: change settings of an existing route (name, date, optimize_for, units, pickup_settings, service_time). Only the fields you pass change. POST /ext-update-route.
| Name | Type | Req | Description |
|---|---|---|---|
| optimize_for | string | – | Optimize for time or distance. |
| pickup_settings | string | – | When pickups are sequenced: auto, before or after. |
| route_date | string | – | New start date, yyyy-mm-dd. |
| route_id | integer | yes | The route to update. |
| route_name | string | – | New route name. |
| service_time | integer | – | Per-stop service (dwell) time in seconds. |
| units | string | – | Distance units: miles or km. |
No output schema declared.
No examples provided.
upper_update_stop Update stop ~495
WRITE: change an existing stop; only the fields you pass change. A new address is re-geocoded (city/state/zipcode you pass with it are ignored); city/state/zipcode apply only without an address. Passing route_id moves the stop to that route. Editing a stop on an optimized route flags the route for re-optimization; stops on an active route cannot be edited. POST /ext-update-stop.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | New street address (re-geocoded). |
| capacity_fields | object | – | Capacity values (integers) for load planning, keys capacity1 - capacity5. |
| city | string | – | City (only used when no address is passed). |
| company_name | string | – | Company name for the stop. |
| contact_name | string | – | Contact (recipient) name. |
| custom_fields | object | – | Custom field values keyed by slot (custom1 - custom5). Only fields enabled in the workspace (and in the plan) are stored. |
| customer_system_id | string | – | Your own identifier for the stop (for cross-referencing). |
| string | – | Contact email. | |
| end_time | string | – | Latest service time (time window end), HH:MM or HH:MM:SS. |
| nick_name | string | – | Short label for the stop. |
| note | string | – | Free-text note shown to the driver. |
| parcel_count | integer | – | Number of parcels at the stop. |
| phone | string | – | Contact phone number; non-digits are stripped by Upper. |
| phone_country_code | string | – | Phone dialing code, for example 1. |
| pin_color | string | – | Map pin colour, hex like #FF6600. |
| route_id | integer | – | Move the stop to this route. |
| start_time | string | – | Earliest service time (time window start), HH:MM or HH:MM:SS. |
| state | string | – | State or region (only used when no address is passed). |
| stop_duration | integer | – | Service duration at the stop, in seconds. |
| stop_id | integer | yes | The stop to update. |
| stop_priority | string | – | Stop priority, for example Normal, High, Urgent. |
| stop_type | string | – | Stop type, for example Delivery or Pickup. |
| zipcode | string | – | Postal code (only used when no address is passed). |
No output schema declared.
No examples provided.
How do I install the Upper Route Planner MCP by usefulapi server?
Upper Route Planner MCP by usefulapi is a hosted endpoint at https://upper-route-planner.usefulapi.io/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 · upper-route-planner.usefulapi.io
claude mcp add --transport http io-usefulapi-upper-route-planner 'https://upper-route-planner.usefulapi.io/mcp'
What is the Upper Route Planner MCP by usefulapi server?
Upper Route Planner MCP by usefulapi is listed in the public MCP registry as io.usefulapi/upper-route-planner. Read Upper drivers and stops; create and optimize routes, assign drivers, share routes to the app. This page covers its hosted endpoint (https://upper-route-planner.usefulapi.io/mcp).
Is the Upper Route Planner MCP by usefulapi server safe to use?
Upper Route Planner MCP by usefulapi scores 18 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 Upper Route Planner MCP by usefulapi server expose?
Upper Route Planner MCP by usefulapi exposes 12 tools: upper_list_drivers, upper_list_stops, upper_get_optimization_status, upper_get_custom_fields, upper_get_capacity_fields, and 7 more. Their descriptions and schemas cost roughly 2,067 tokens of context every time the server is loaded.
Does the Upper Route Planner MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Upper Route Planner MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Upper Route Planner MCP by usefulapi server still maintained?
Upper Route Planner MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 Upper Route Planner MCP by usefulapi server?
VerifyMCP ran 4 checks on Upper Route Planner MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Upper Route Planner MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.