# Spoke Dispatch MCP by usefulapi (remote · spoke-dispatch.usefulapi.io)

Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `spoke-dispatch.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-spoke-dispatch/spoke-dispatch.md), [page](https://verifymcp.io/servers/io-usefulapi-spoke-dispatch/spoke-dispatch)

## Channel facts

- Endpoint: `https://spoke-dispatch.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 82/100
  - 100% 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 2602 tokens (~113/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Spoke Dispatch MCP by usefulapi server?

Spoke Dispatch MCP by usefulapi is a hosted endpoint at https://spoke-dispatch.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-spoke-dispatch 'https://spoke-dispatch.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-spoke-dispatch": {
      "url": "https://spoke-dispatch.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-spoke-dispatch": {
      "type": "http",
      "url": "https://spoke-dispatch.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-spoke-dispatch]
url = "https://spoke-dispatch.usefulapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usefulapi-spoke-dispatch --url 'https://spoke-dispatch.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-spoke-dispatch:
    url: "https://spoke-dispatch.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-spoke-dispatch": {
      "Transport": "http",
      "Url": "https://spoke-dispatch.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-spoke-dispatch -t streamable-http -u 'https://spoke-dispatch.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-spoke-dispatch": {
      "type": "http",
      "url": "https://spoke-dispatch.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-10-17 (score 64, +1)

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

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (23)

### `spoke_list_plans` (~190 tokens)

List plans

List route plans (a plan = one day's delivery job: date, depot, drivers, routes), newest first, in pages of up to 20. Filter with e.g. {"title":"Monday run"} or {"startsGte":"2026-10-01"}. GET /plans.

Input parameters:

- `filter` (object): Extra filter fields as documented by Spoke (name -> value), e.g. {"startsGte":"2026-10-01"}.
- `max_page_size` (integer): Results per page, 1-20 (default 10).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.
- `starts_on_or_after` (string): Only plans starting on or after this date (yyyy-mm-dd).
- `title` (string): Only plans with this title.

### `spoke_get_plan` (~69 tokens)

Get plan

One plan: title, start date, depot, driver ids, route ids, whether it is distributed/writable, optimization state and route overrides. GET /plans/{planId}.

Input parameters:

- `plan_id` (string, required): Plan id, e.g. 'abc123' or 'plans/abc123'.

### `spoke_list_plan_stops` (~134 tokens)

List plan stops

List the stops of a plan, in pages of up to 10. Stops include recipient names, phones, e-mails and addresses (personal data): page only as far as needed. GET /plans/{planId}/stops.

Input parameters:

- `max_page_size` (integer): Results per page, 1-10 (default 10).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.
- `plan_id` (string, required)
- `recipient_external_id` (string): Only stops whose recipient has this external id.

### `spoke_get_stop` (~91 tokens)

Get stop

One stop of a plan with address, recipient, timing, ETA, route and delivery outcome (attempted, succeeded, notes, photo/signature links). Contains personal data. GET /plans/{planId}/stops/{stopId}.

Input parameters:

- `plan_id` (string, required)
- `stop_id` (string, required): Stop id, e.g. 'xyz' or 'plans/abc/stops/xyz'.

### `spoke_search_stops` (~243 tokens)

Search stops

Search all stops of the team (planned, unassigned, past) by keyword and/or Spoke's filter language, up to 20 per page. Example filter: address.countryCode = "DE" and deliveryInfo.attempted = false. Filterable: planId, routeId, type, activity, notes, address.*, createdAt, recipient.name/email/phone/externalId, deliveryInfo.state/attempted/succeeded, orderInfo.*. Results include personal data. The search index lags real time by a short while. GET /stops:search.

Input parameters:

- `filter` (string): Spoke filter expression, e.g. createdAt >= "2026-10-01T00:00:00Z" and address ~= "London".
- `keyword` (string): Fuzzy full-text keywords.
- `max_page_size` (integer): Results per page, 1-20 (default 20).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.
- `sort_field` (string)
- `sort_order` (string)

### `spoke_list_unassigned_stops` (~101 tokens)

List unassigned stops

List stops that are not on any plan yet (the inbox of imported orders), in pages of up to 20 (default 20). Contains personal data. GET /unassignedStops.

Input parameters:

- `max_page_size` (integer): Results per page, 1-20 (default 20).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.

### `spoke_get_unassigned_stop` (~55 tokens)

Get unassigned stop

One unassigned stop by id. Contains personal data. GET /unassignedStops/{id}.

Input parameters:

- `unassigned_stop_id` (string, required): Id, e.g. 'abc' or 'unassignedStops/abc'.

### `spoke_list_drivers` (~115 tokens)

List drivers

List the team's drivers (name, e-mail/phone, active flag, depots, route overrides), up to 50 per page. Contains personal data. GET /drivers.

Input parameters:

- `active` (boolean): Only active (true) or inactive (false) drivers.
- `max_page_size` (integer): Results per page, 1-50 (default 50).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.

### `spoke_get_driver` (~47 tokens)

Get driver

One driver by id. Contains personal data. GET /drivers/{driverId}.

Input parameters:

- `driver_id` (string, required): Driver id, e.g. 'abc' or 'drivers/abc'.

### `spoke_list_depots` (~97 tokens)

List depots

List depots (start/end addresses, working hours, vehicle type, max stops), up to 20 per page. Use the ids when creating plans. GET /depots.

Input parameters:

- `max_page_size` (integer): Results per page, 1-20 (default 20).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.

### `spoke_get_depot` (~47 tokens)

Get depot

One depot by id. GET /depots/{depotId}.

Input parameters:

- `depot_id` (string, required): Depot id, e.g. 'abc' or 'depots/abc'.

### `spoke_list_routes` (~117 tokens)

List routes

List routes (one driver's run of a plan: stop count, driver, distributed/started/completed state), up to 20 per page. GET /routes.

Input parameters:

- `max_page_size` (integer): Results per page, 1-20 (default 20).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.
- `starts_on_or_after` (string): Only routes of plans starting on or after this date (yyyy-mm-dd).

### `spoke_get_route` (~59 tokens)

Get route

One route: title, driver, stop count and state (distributed, started, completed, recipients notified). GET /routes/{routeId}.

Input parameters:

- `route_id` (string, required): Route id, e.g. 'abc' or 'routes/abc'.

### `spoke_list_route_stops` (~126 tokens)

List route stops

List the stops of one route in driving order, in pages of up to 10. Contains personal data: page only as far as needed. GET /routes/{routeId}/stops.

Input parameters:

- `max_page_size` (integer): Results per page, 1-10 (default 10).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.
- `recipient_external_id` (string): Only stops whose recipient has this external id.
- `route_id` (string, required)

### `spoke_list_operations` (~96 tokens)

List operations

List long-running operations (plan optimizations): type, done flag, who started it, result (optimized and skipped stops), up to 20 per page. GET /operations.

Input parameters:

- `max_page_size` (integer): Results per page, 1-20 (default 20).
- `page_token` (string): Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page.

### `spoke_get_operation` (~59 tokens)

Get operation

One operation, e.g. the optimization started by spoke_optimize_plan: poll until done is true. GET /operations/{operationId}.

Input parameters:

- `operation_id` (string, required): Operation id, e.g. 'abc' or 'operations/abc'.

### `spoke_list_custom_stop_properties` (~53 tokens)

List custom stop properties

The team's custom stop property definitions (ids and names). Their ids are the keys of customProperties on stops. Needs a subscription that includes custom properties (HTTP 403 otherwise). GET /team/customStopProperties.

### `spoke_create_plan` (~142 tokens)

Create plan

WRITE: create a new route plan for a date (no stops yet, nothing is sent to drivers). Optionally assign drivers (up to 50, they must be active and share the plan's depot) and a depot (default: the team's main depot). Does not optimize or distribute. POST /plans.

Input parameters:

- `depot_id` (string): Depot id ('abc' or 'depots/abc').
- `driver_ids` (array): Driver ids ('abc' or 'drivers/abc').
- `starts_on` (string, required): Plan date, yyyy-mm-dd (Spoke rejects dates too far in the past or future).
- `title` (string, required)

### `spoke_update_plan` (~119 tokens)

Update plan

WRITE: change a plan's title, date, drivers and/or depot. Only the fields you pass change, but driver_ids REPLACES the plan's whole driver list. Fails if the plan is not writable (already distributed). Nothing is sent to drivers. PATCH /plans/{planId}.

Input parameters:

- `depot_id` (string)
- `driver_ids` (array): The complete new driver list (replaces the old one).
- `plan_id` (string, required)
- `starts_on` (string)
- `title` (string)

### `spoke_create_stop` (~98 tokens)

Create stop

WRITE: add one stop to a writable (not yet distributed) plan. Needs an address (text fields or latitude+longitude). The recipient's phone/e-mail are stored on the stop and Spoke may contact the recipient later when the route runs; nothing is sent now. For many stops use spoke_import_stops. POST /plans/{planId}/stops.

Input parameters:

- `plan_id` (string, required)
- `stop` (object, required)

### `spoke_import_stops` (~102 tokens)

Import stops

WRITE: add up to 100 stops to a writable (not yet distributed) plan in one request (better geocoding than one at a time; Spoke limits imports to 30 requests a minute). Returns the created stop ids and any failures. Recipient contact data is stored on the stops; nothing is sent now. POST /plans/{planId}/stops:import.

Input parameters:

- `plan_id` (string, required)
- `stops` (array, required)

### `spoke_optimize_plan` (~105 tokens)

Optimize plan

WRITE: start the route optimization of a plan (orders and assigns its stops to its drivers). Rewrites the plan's routes if it was optimized before, and uses Spoke's optimization quota (30 per minute, 100 per 10 minutes). Does NOT send anything to drivers. Returns an operation: poll spoke_get_operation until done. Needs at least one driver and one stop. POST /plans/{planId}:optimize.

Input parameters:

- `plan_id` (string, required)

### `spoke_distribute_plan` (~133 tokens)

Distribute plan to drivers

WRITE (SENDS TO REAL PEOPLE): distribute an optimized plan, which immediately sends each driver of the plan their route on their phone (push notification / message) and locks the plan for edits. Cannot be undone. Only for a plan with 1-10 drivers, and only after the user has explicitly said to send the routes: set confirm_send_to_drivers to true. POST /plans/{planId}:distribute.

Input parameters:

- `confirm_send_to_drivers` (boolean, required): Must be true: confirms the user asked to send the routes to the plan's drivers now.
- `plan_id` (string, required)

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the Spoke Dispatch MCP by usefulapi server?

Spoke Dispatch MCP by usefulapi is listed in the public MCP registry as io.usefulapi/spoke-dispatch. Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes. This page covers its hosted endpoint (https://spoke-dispatch.usefulapi.io/mcp).

### Is the Spoke Dispatch MCP by usefulapi server safe to use?

Spoke Dispatch MCP by usefulapi scores 64 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 Spoke Dispatch MCP by usefulapi server expose?

Spoke Dispatch MCP by usefulapi exposes 23 tools: spoke_list_plans, spoke_get_plan, spoke_list_plan_stops, spoke_get_stop, spoke_search_stops, and 18 more. Their descriptions and schemas cost roughly 2,398 tokens of context every time the server is loaded.

### Does the Spoke Dispatch MCP by usefulapi server require authentication?

Yes. Spoke Dispatch MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Spoke Dispatch MCP by usefulapi server still maintained?

Spoke Dispatch MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://spoke-dispatch.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/spoke-dispatch/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-spoke-dispatch/spoke-dispatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-spoke-dispatch/spoke-dispatch.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-spoke-dispatch/spoke-dispatch