# Delivery Planner by Spoke (remote · deliveryplanner.com)

Plan and optimize a multi-stop delivery route, then share it with your driver.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `deliveryplanner.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-deliveryplanner-delivery-planner/api-free-route-planner-mcp.md), [page](https://verifymcp.io/servers/com-deliveryplanner-delivery-planner/api-free-route-planner-mcp)

## Channel facts

- Endpoint: `https://deliveryplanner.com/api/free-route-planner/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 50/100
  - 33% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1398 tokens (~155/item across 9 items; 6 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Delivery Planner by Spoke MCP server?

Delivery Planner by Spoke is a hosted endpoint at https://deliveryplanner.com/api/free-route-planner/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 com-deliveryplanner-delivery-planner 'https://deliveryplanner.com/api/free-route-planner/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-deliveryplanner-delivery-planner": {
      "url": "https://deliveryplanner.com/api/free-route-planner/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-deliveryplanner-delivery-planner": {
      "type": "http",
      "url": "https://deliveryplanner.com/api/free-route-planner/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-deliveryplanner-delivery-planner]
url = "https://deliveryplanner.com/api/free-route-planner/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-deliveryplanner-delivery-planner": {
      "type": "remote",
      "url": "https://deliveryplanner.com/api/free-route-planner/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-deliveryplanner-delivery-planner --url 'https://deliveryplanner.com/api/free-route-planner/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-deliveryplanner-delivery-planner:
    url: "https://deliveryplanner.com/api/free-route-planner/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-deliveryplanner-delivery-planner": {
      "Transport": "http",
      "Url": "https://deliveryplanner.com/api/free-route-planner/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-deliveryplanner-delivery-planner -t streamable-http -u 'https://deliveryplanner.com/api/free-route-planner/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-deliveryplanner-delivery-planner": {
      "type": "http",
      "url": "https://deliveryplanner.com/api/free-route-planner/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-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 71, 0)

- [security] Tool “confirm_route” rewrote its description, which is the text the model reads

### 2026-11-10 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `search_places` (~139 tokens)

Find delivery addresses

Finds Google address suggestions, with place IDs, for one address or place name. Use this when a user wants to plan deliveries, order driving stops, or optimize a multi-stop driving route and provides addresses or place names, including pasted spreadsheets, tables, CSV, or numbered lists. Suggestions come from autocomplete and are not validated addresses. Not for general place recommendations, package tracking, or public-transit directions.

Input parameters:

- `locationBias` (object): Optional search-area coordinates from the user or a verified location source. Biases suggestions toward this area without restricting them to it. Radius is in metres and defaults to 5000.
- `query` (string, required)

Output parameters:

- `places` (array)

### `create_route` (~170 tokens)

Plan a delivery route with Spoke

Optimizes and saves one driving route for one driver with 1–20 delivery stops, from the addresses and settings the user confirmed in the address panel. Use this when a user asks what order to visit delivery addresses, wants an efficient driving route between multiple stops, or wants a route they can open and share. Takes the single-use token the panel issues when the user clicks Optimize route. Returns the stops in optimized order, estimated duration and distance, the route geometry, and route links. Every call creates a new route, and anyone with the returned link can view its addresses. Does not enforce delivery time windows, and not for package tracking, public transit, multiple drivers, or live-traffic estimates.

Input parameters:

- `confirmationToken` (string): Single-use token returned when the user clicks Optimize in the address panel.

Output parameters:

- `dispatchUrl` (string)
- `distanceMeters` (number)
- `distanceUnit` (string)
- `driverUrl` (string)
- `durationMinutes` (number)
- `encodedPolyline` (string): Saved driving route overview in Google encoded polyline format (precision 5). Empty when route geometry is unavailable.
- `estimateNotice` (string)
- `ignoredFields` (array)
- `routeUrl` (string)
- `startTime` (string|null)
- `stops` (array)
- `timeAtStopMinutes` (number)

### `confirm_route` (~167 tokens)

Confirm reviewed route

Called by the address panel when the user clicks Optimize. Records the chosen addresses and route settings and returns the single-use confirmationToken that create_route takes. Not for direct model use.

Input parameters:

- `distanceUnit` (string)
- `endPlaceId` (string): Omit to return to the start location.
- `ignoredFields` (array): Unsupported input fields excluded from optimization, listed in the result.
- `startPlaceId` (string, required): Start location returned by search_places.
- `startTime`: Departure date/time with UTC offset; null when unspecified. Does not change traffic estimates.
- `stopPlaceIds` (array, required): Unordered delivery locations returned by search_places. Array position does not constrain visit order; the optimizer reorders these stops.
- `timeAtStopMinutes` (integer)

### `select_addresses` (~151 tokens)

Choose addresses and route settings

Shows a panel where the user picks a match for each address and sets the start, finish, time at each stop and distance unit. Takes each original address with its suggested matches; addresses without suggestions let the user search again in the panel. Missing start and finish appear as empty fields, and fields in routeSettings.ignoredFields are listed as not applied. Read-only: when the user clicks Optimize, the panel issues a single-use confirmation token for route creation.

Input parameters:

- `addresses` (array, required)
- `routeSettings` (object): Initial route settings. The form collects start, end (or a return to the start), time at stop and distance unit, and adds empty start and finish fields when they are missing.

Output parameters:

- `addresses` (array)
- `dispatchUrl` (string)
- `ignoredFieldLabels` (array)
- `routeSettings` (object): Initial route settings. The form collects start, end (or a return to the start), time at stop and distance unit, and adds empty start and finish fields when they are missing.

### `show_dispatch_options` (~85 tokens)

More delivery planning options

Shows a link to Spoke Dispatch, our route planner for teams, for needs this free planner does not cover: multiple drivers, enforced delivery time windows, or more than 20 delivery stops. Use this only when the user explicitly asks for one of those. It only displays the link; it does not transfer addresses or create a Dispatch account.

Input parameters:

- `reason` (string, required)

### `resolve_current_location` (~44 tokens)

Find starting address from current location

Returns the nearest address for coordinates from the Use current location button in the panel, to fill the start.

Input parameters:

- `latitude` (number, required)
- `longitude` (number, required)

Output parameters:

- `places` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-deliveryplanner-delivery-planner/api-free-route-planner-mcp#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71
- 2026-11-10: 71
- 2026-11-09: 70
- 2026-11-08: 70
- 2026-11-07: 69
- 2026-11-06: 69
- 2026-11-05: 68
- 2026-11-04: 68

## Common questions

### What is the Delivery Planner by Spoke MCP server?

Delivery Planner by Spoke is an MCP server listed in the public MCP registry as com.deliveryplanner/delivery-planner. Plan and optimize a multi-stop delivery route, then share it with your driver. This page covers its hosted endpoint (https://deliveryplanner.com/api/free-route-planner/mcp).

### Is the Delivery Planner by Spoke MCP server safe to use?

Delivery Planner by Spoke scores 76 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 Delivery Planner by Spoke MCP server expose?

Delivery Planner by Spoke exposes 6 tools: search_places, create_route, confirm_route, select_addresses, show_dispatch_options, resolve_current_location. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

### Does the Delivery Planner by Spoke MCP server require authentication?

No. We connected to Delivery Planner by Spoke without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Delivery Planner by Spoke MCP server still maintained?

Delivery Planner by Spoke 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 Delivery Planner by Spoke MCP server?

VerifyMCP ran 14 checks on Delivery Planner by Spoke, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.

## Links

- Remote endpoint: https://deliveryplanner.com/api/free-route-planner/mcp
- Website: https://deliveryplanner.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-deliveryplanner-delivery-planner/api-free-route-planner-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-deliveryplanner-delivery-planner/api-free-route-planner-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-deliveryplanner-delivery-planner/api-free-route-planner-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-deliveryplanner-delivery-planner/api-free-route-planner-mcp
