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
Shipday 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.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Shipday orders, carriers and delivery status; create orders and assign drivers.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http shipday-mcp-by-usefulapi https://shipday.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# list_active_orders, get_order, query_orders and 11 more
Shipday 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 shipday-mcp-by-usefulapi https://shipday.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
14 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 the account's active (not yet completed) delivery orders with customer, pickup location (restaurant), assigned carrier/driver, timeline (activityLog), costs, payment method and orderStatus.orderState. Good first call. Shipday: GET /orders.
No parameter schema on file.
Get the details of a delivery order by its order number (the merchant's reference, orderNumber). Returns an array, since several orders can share one order number. Includes the numeric orderId needed by the write tools, the carrier, tracking link and status. Shipday: GET /orders/{orderNumber}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The order number (orderNumber) of the order, e.g. "75637". |
Search delivery orders, including completed ones, by placement-time window and status, with row-based paging: start_cursor/end_cursor select rows (e.g. 1–100, then 101–200; at most 100 per call) sorted newest first. Each row has timestamps (placement, assigned, picked up, delivered, failed), totals, driver payment, distance and carrier. Shipday: POST /orders/query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_time | string | no | Only orders placed at/after this ISO 8601 time (UTC), e.g. 2026-10-01T00:00:00Z. |
| end_time | string | no | Only orders placed at/before this ISO 8601 time (UTC). |
| order_status | string | no | Only orders in this status. |
| start_cursor | integer | no | First row to return (1-based, default 1). |
| end_cursor | integer | no | Last row to return (default start_cursor + 99). At most 100 rows per call. |
Get a pickup (customer collects it) order by its numeric id, with restaurant, customer, items, costs, expected pickup date/time and status. Shipday: GET /pickup-orders/{orderId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Numeric id of the pickup order. |
Real-time delivery progress of an order by its tracking id: status (STARTED, PICKED_UP, ...), timestamps, the driver's current location and the ETA in minutes. The tracking id is the last part of the order's trackingLink. Shipday's Business Advanced plan only; at most 3 requests per minute per tracking id. Shipday: GET /order/progress/{trackingId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tracking_id | string | yes | The order's tracking id (from its trackingLink). |
| include_static_data | boolean | no | true = also return fixed details (customer, restaurant, carrier). Default false. |
List the account's carriers (drivers) with id, name, phone, email, isOnShift, isActive and last known location. Use an id here with assign_order_to_carrier. Shipday: GET /carriers.
No parameter schema on file.
List the third-party on-demand delivery services (DoorDash, Uber, ...) available to the account and whether each is enabled. Shipday: GET /on-demand/services.
No parameter schema on file.
Get fee and time estimates from the third-party on-demand delivery services for an existing order (fee, pickup/delivery time, durations, per-service errors). Read only: nothing is booked. Shipday: GET /on-demand/estimate/{orderId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the orderId field, not the order number). |
Details of the third-party on-demand delivery booked for an order: provider, reference id, third-party fee, Shipday charge, total billable amount and tracking URL. Shipday: GET /on-demand/details/{orderId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the orderId field, not the order number). |
Quote third-party on-demand delivery for a pickup and delivery address before creating an order: which services can deliver, their fee and pickup/delivery times. Read only: nothing is booked. Shipday: POST /on-demand/availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pickup_address | string | yes | Full pickup address. |
| delivery_address | string | yes | Full delivery address. |
| pickup_time | string | no | Expected pickup time, ISO 8601 UTC. |
| delivery_time | string | no | Expected delivery time, ISO 8601 UTC. |
WRITE: insert a new delivery order into Shipday (it appears on the dispatch board; it is not assigned to a driver). Returns the new orderId. Times are UTC. Shipday: POST /orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | Your reference for the order (orderNumber). |
| customer_name | string | yes | Customer name. |
| customer_address | string | yes | Delivery address. |
| customer_phone_number | string | yes | Customer phone number with country code, e.g. +14155550100. |
| customer_email | string | no | Customer email. |
| restaurant_name | string | yes | Pickup location / store name. |
| restaurant_address | string | yes | Pickup address. |
| restaurant_phone_number | string | no | Pickup location phone with country code. |
| expected_delivery_date | string | no | Expected delivery date, yyyy-mm-dd (UTC). |
| expected_pickup_time | string | no | Expected pickup time, hh:mm:ss (UTC). |
| expected_delivery_time | string | no | Expected delivery time, hh:mm:ss (UTC). |
| pickup_latitude | number | no | Pickup latitude. |
| pickup_longitude | number | no | Pickup longitude. |
| delivery_latitude | number | no | Delivery latitude. |
| delivery_longitude | number | no | Delivery longitude. |
| order_items | array | no | Items in the order. |
| tips | number | no | Tip amount. |
| tax | number | no | Tax amount. |
| discount_amount | number | no | Discount amount. |
| delivery_fee | number | no | Delivery fee. |
WRITE: assign a delivery order to one of the account's own carriers (drivers); the driver is notified in the Shipday driver app. Re-assigning to the same driver changes nothing. Shipday: PUT /orders/assign/{orderId}/{carrierId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the orderId field, not the order number). |
| carrier_id | integer | yes | Numeric carrier (driver) id from list_carriers. |
WRITE: remove the driver from a delivery order (it goes back to unassigned). Shipday: PUT /orders/unassign/{orderId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the orderId field, not the order number). |
WRITE: set or clear an order's ready-to-pickup flag (tells the driver the order is ready at the pickup location). Shipday: PUT /orders/{orderId}/meta.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the orderId field, not the order number). |
| ready_to_pickup | boolean | no | true = ready (default), false = not ready. |
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 Shipday 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.2.1.
1.2.1
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 Shipday 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.