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

- Trust score: 18/100 (low)
- Change this week: −46
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `upper-route-planner.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-upper-route-planner/upper-route-planner.md), [page](https://verifymcp.io/servers/io-usefulapi-upper-route-planner/upper-route-planner)

## Channel facts

- Endpoint: `https://upper-route-planner.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.11.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

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

### Claude

```bash
claude mcp add --transport http io-usefulapi-upper-route-planner 'https://upper-route-planner.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-upper-route-planner": {
      "url": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-upper-route-planner": {
      "type": "http",
      "url": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-upper-route-planner]
url = "https://upper-route-planner.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-upper-route-planner": {
      "type": "remote",
      "url": "https://upper-route-planner.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-upper-route-planner --url 'https://upper-route-planner.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-upper-route-planner:
    url: "https://upper-route-planner.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-upper-route-planner": {
      "Transport": "http",
      "Url": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-upper-route-planner -t streamable-http -u 'https://upper-route-planner.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-upper-route-planner": {
      "type": "http",
      "url": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-02 (score 18, −49)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 67, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] 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

### 2026-10-30 (score 64, +1)

- [functional] Server version: 1.5.1 → 1.5.2
- [functional] Server version: 1.5.0 → 1.5.1

### 2026-10-29 (score 63, 0)

- [functional] Server version: 1.4.0 → 1.5.0
- [functional] Server version: 1.3.0 → 1.4.0

### 2026-10-28 (score 63, +1)

- [functional] Server version: 1.1.0 → 1.3.0

### 2026-10-27 (score 62, 0)

- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-26 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (12)

### `upper_list_drivers` (~55 tokens)

List drivers

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.

### `upper_list_stops` (~226 tokens)

List stops

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.

Input parameters:

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

### `upper_get_optimization_status` (~67 tokens)

Get route optimization status

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.

Input parameters:

- `route_id` (integer, required): The route id.

### `upper_get_custom_fields` (~55 tokens)

Get stop custom fields

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.

### `upper_get_capacity_fields` (~43 tokens)

Get capacity fields

The workspace's five capacity-field slots (capacity1 - capacity5: label, unit, enabled) used for load planning. GET /ext-get-capacity-fields.

### `upper_create_route` (~168 tokens)

Create route

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.

Input parameters:

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

### `upper_update_route` (~147 tokens)

Update route

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.

Input parameters:

- `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, required): 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.

### `upper_create_stop` (~474 tokens)

Create stop

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.

Input parameters:

- `address` (string, required): 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).
- `email` (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).

### `upper_update_stop` (~495 tokens)

Update stop

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.

Input parameters:

- `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).
- `email` (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, required): 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).

### `upper_assign_drivers` (~103 tokens)

Assign drivers to a route

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.

Input parameters:

- `driver_ids` (array, required): Driver ids to assign.
- `route_id` (integer, required): The route.

### `upper_optimize_route` (~109 tokens)

Optimize route

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.

Input parameters:

- `route_id` (integer, required): The route to optimize.
- `timezone` (string): IANA timezone for the optimization, for example America/New_York.

### `upper_share_route_to_drivers` (~125 tokens)

Share route to drivers

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.

Input parameters:

- `driver_ids` (array): Drivers to notify (default: the route's assigned drivers).
- `route_id` (integer, required): The route to share.
- `timezone` (string): IANA timezone, for example America/New_York.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-upper-route-planner/upper-route-planner#diagnostics

## Score history

- 2026-11-06: 18
- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 64
- 2026-10-29: 63
- 2026-10-28: 63
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 61

## Common questions

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

## Links

- Remote endpoint: https://upper-route-planner.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/upper-route-planner/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-upper-route-planner/upper-route-planner.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-upper-route-planner/upper-route-planner/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-upper-route-planner/upper-route-planner.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-upper-route-planner/upper-route-planner