Spoke Dispatch MCP by usefulapi
REMOTE · SPOKE-DISPATCH.USEFULAPI.IO
Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes.
Available components
Last scanned (2 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Workflow Automation
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
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 17 Oct 2026 · Probed https://spoke-dispatch.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 spoke-dispatch.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://spoke-dispatch.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://spoke-dispatch.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://spoke-dispatch.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://spoke-dispatch.usefulapi.io/mcp |
| Authorisation server | https://spoke-dispatch.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spoke-dispatch.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/spoke-dispatch/ |
| http (plaintext) | http://spoke-dispatch.usefulapi.io/mcp | Inconclusive | 302 | http://spoke-dispatch.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 →
spoke_create_plan Create plan ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depot_id | string | – | Depot id ('abc' or 'depots/abc'). |
| driver_ids | array | – | Driver ids ('abc' or 'drivers/abc'). |
| starts_on | string | yes | Plan date, yyyy-mm-dd (Spoke rejects dates too far in the past or future). |
| title | string | yes | – |
No output schema declared.
No examples provided.
spoke_create_stop Create stop ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
| stop | object | yes | – |
No output schema declared.
No examples provided.
spoke_distribute_plan Distribute plan to drivers ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_send_to_drivers | boolean | yes | Must be true: confirms the user asked to send the routes to the plan's drivers now. |
| plan_id | string | yes | – |
No output schema declared.
No examples provided.
spoke_get_depot Get depot ~47
One depot by id. GET /depots/{depotId}.
| Name | Type | Req | Description |
|---|---|---|---|
| depot_id | string | yes | Depot id, e.g. 'abc' or 'depots/abc'. |
No output schema declared.
No examples provided.
spoke_get_driver Get driver ~47
One driver by id. Contains personal data. GET /drivers/{driverId}.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_id | string | yes | Driver id, e.g. 'abc' or 'drivers/abc'. |
No output schema declared.
No examples provided.
spoke_get_operation Get operation ~59
One operation, e.g. the optimization started by spoke_optimize_plan: poll until done is true. GET /operations/{operationId}.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | Operation id, e.g. 'abc' or 'operations/abc'. |
No output schema declared.
No examples provided.
spoke_get_plan Get plan ~69
One plan: title, start date, depot, driver ids, route ids, whether it is distributed/writable, optimization state and route overrides. GET /plans/{planId}.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | Plan id, e.g. 'abc123' or 'plans/abc123'. |
No output schema declared.
No examples provided.
spoke_get_route Get route ~59
One route: title, driver, stop count and state (distributed, started, completed, recipients notified). GET /routes/{routeId}.
| Name | Type | Req | Description |
|---|---|---|---|
| route_id | string | yes | Route id, e.g. 'abc' or 'routes/abc'. |
No output schema declared.
No examples provided.
spoke_get_stop Get stop ~91
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
| stop_id | string | yes | Stop id, e.g. 'xyz' or 'plans/abc/stops/xyz'. |
No output schema declared.
No examples provided.
spoke_get_unassigned_stop Get unassigned stop ~55
One unassigned stop by id. Contains personal data. GET /unassignedStops/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| unassigned_stop_id | string | yes | Id, e.g. 'abc' or 'unassignedStops/abc'. |
No output schema declared.
No examples provided.
spoke_import_stops Import stops ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
| stops | array | yes | – |
No output schema declared.
No examples provided.
spoke_list_custom_stop_properties List custom stop properties ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spoke_list_depots List depots ~97
List depots (start/end addresses, working hours, vehicle type, max stops), up to 20 per page. Use the ids when creating plans. GET /depots.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
spoke_list_drivers List drivers ~115
List the team's drivers (name, e-mail/phone, active flag, depots, route overrides), up to 50 per page. Contains personal data. GET /drivers.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
spoke_list_operations List operations ~96
List long-running operations (plan optimizations): type, done flag, who started it, result (optimized and skipped stops), up to 20 per page. GET /operations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
spoke_list_plan_stops List plan stops ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| recipient_external_id | string | – | Only stops whose recipient has this external id. |
No output schema declared.
No examples provided.
spoke_list_plans List plans ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
spoke_list_route_stops List route stops ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
spoke_list_routes List routes ~117
List routes (one driver's run of a plan: stop count, driver, distributed/started/completed state), up to 20 per page. GET /routes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
spoke_list_unassigned_stops List unassigned stops ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
spoke_optimize_plan Optimize plan ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
No output schema declared.
No examples provided.
spoke_search_stops Search stops ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
spoke_update_plan Update plan ~119
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| depot_id | string | – | – |
| driver_ids | array | – | The complete new driver list (replaces the old one). |
| plan_id | string | yes | – |
| starts_on | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
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.
remote · spoke-dispatch.usefulapi.io
claude mcp add --transport http io-usefulapi-spoke-dispatch 'https://spoke-dispatch.usefulapi.io/mcp'
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.