Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Spoke Dispatch MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
23
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http spoke-dispatch-mcp-by-usefulapi https://spoke-dispatch.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# spoke_list_plans, spoke_get_plan, spoke_list_plan_stops and 20 more
Spoke Dispatch MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http spoke-dispatch-mcp-by-usefulapi https://spoke-dispatch.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | no | Only plans with this title. |
| starts_on_or_after | string | no | Only plans starting on or after this date (yyyy-mm-dd). |
| filter | object | no | Extra filter fields as documented by Spoke (name -> value), e.g. {"startsGte":"2026-10-01"}. |
| max_page_size | integer | no | Results per page, 1-20 (default 10). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
One plan: title, start date, depot, driver ids, route ids, whether it is distributed/writable, optimization state and route overrides. GET /plans/{planId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | Plan id, e.g. 'abc123' or 'plans/abc123'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
| recipient_external_id | string | no | Only stops whose recipient has this external id. |
| max_page_size | integer | no | Results per page, 1-10 (default 10). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
| stop_id | string | yes | Stop id, e.g. 'xyz' or 'plans/abc/stops/xyz'. |
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 s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | no | Fuzzy full-text keywords. |
| filter | string | no | Spoke filter expression, e.g. createdAt >= "2026-10-01T00:00:00Z" and address ~= "London". |
| sort_field | string | no | — |
| sort_order | string | no | — |
| max_page_size | integer | no | Results per page, 1-20 (default 20). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_page_size | integer | no | Results per page, 1-20 (default 20). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
One unassigned stop by id. Contains personal data. GET /unassignedStops/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| unassigned_stop_id | string | yes | Id, e.g. 'abc' or 'unassignedStops/abc'. |
List the team's drivers (name, e-mail/phone, active flag, depots, route overrides), up to 50 per page. Contains personal data. GET /drivers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| active | boolean | no | Only active (true) or inactive (false) drivers. |
| max_page_size | integer | no | Results per page, 1-50 (default 50). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
One driver by id. Contains personal data. GET /drivers/{driverId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| driver_id | string | yes | Driver id, e.g. 'abc' or 'drivers/abc'. |
List depots (start/end addresses, working hours, vehicle type, max stops), up to 20 per page. Use the ids when creating plans. GET /depots.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_page_size | integer | no | Results per page, 1-20 (default 20). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
One depot by id. GET /depots/{depotId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| depot_id | string | yes | Depot id, e.g. 'abc' or 'depots/abc'. |
List routes (one driver's run of a plan: stop count, driver, distributed/started/completed state), up to 20 per page. GET /routes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| starts_on_or_after | string | no | Only routes of plans starting on or after this date (yyyy-mm-dd). |
| max_page_size | integer | no | Results per page, 1-20 (default 20). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
One route: title, driver, stop count and state (distributed, started, completed, recipients notified). GET /routes/{routeId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route_id | string | yes | Route id, e.g. 'abc' or 'routes/abc'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route_id | string | yes | — |
| recipient_external_id | string | no | Only stops whose recipient has this external id. |
| max_page_size | integer | no | Results per page, 1-10 (default 10). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
List long-running operations (plan optimizations): type, done flag, who started it, result (optimized and skipped stops), up to 20 per page. GET /operations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_page_size | integer | no | Results per page, 1-20 (default 20). |
| page_token | string | no | Page token: pass the previous reply's nextPageToken (with the same other arguments) for the next page. |
One operation, e.g. the optimization started by spoke_optimize_plan: poll until done is true. GET /operations/{operationId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | Operation id, e.g. 'abc' or 'operations/abc'. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | — |
| starts_on | string | yes | Plan date, yyyy-mm-dd (Spoke rejects dates too far in the past or future). |
| driver_ids | array | no | Driver ids ('abc' or 'drivers/abc'). |
| depot_id | string | no | Depot id ('abc' or 'depots/abc'). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
| title | string | no | — |
| starts_on | string | no | — |
| driver_ids | array | no | The complete new driver list (replaces the old one). |
| depot_id | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
| stop | object | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
| stops | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
| confirm_send_to_drivers | boolean | yes | Must be true: confirms the user asked to send the routes to the plan's drivers now. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Spoke Dispatch MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Spoke Dispatch MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.