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
Track-POD 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.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Track-POD orders, routes, drivers, vehicles and proof of delivery; create orders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http track-pod-mcp-by-usefulapi https://track-pod.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# trackpod_list_orders, trackpod_list_orders_changed_since, trackpod_list_route_orders and 13 more
Track-POD 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 track-pod-mcp-by-usefulapi https://track-pod.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
16 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 orders of one day — by order date (GET /Order/Date/{date}) or by planned route date (GET /Order/Route/Date/{date}) — with optional filters on delivery status, driver and route number. Track-POD returns the whole day at once; this tool pages it (offset/limit) and reports the total. Times are the account's local times.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | The day, YYYY-MM-DD. |
| date_type | string | no | order_date (default): orders whose order date is this day, scheduled or not. route_date: orders planned into routes of this day. |
| status | array | no | Keep only orders with these delivery statuses: no_status (not yet attempted / unassigned), in_progress (1), not_delivered_site_issue (2), delivered (3, also 'collected'), partially (4), not_delivered_ |
| driver | string | no | Keep only orders whose driver login or name contains this text. |
| route_number | string | no | Keep only orders on this route number/code. |
| detail | string | no | summary (default): key fields per order. full: every field Track-POD returns (goods lines, custom fields, photo links). |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Items per page (default 25, max 100). |
List orders whose delivery status changed after a moment in the last 24 hours (GET /Order/Status/Date/{date-time}; Track-POD accepts no earlier time than UTC now − 1 day). Good for 'what was delivered / failed since this morning'. Paged here (offset/limit).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | ISO 8601 date-time with a timezone, within the last 24 hours, e.g. 2026-10-08T06:00:00Z. Default: 23 h 59 min ago. |
| status | array | no | Keep only orders with these delivery statuses: no_status (not yet attempted / unassigned), in_progress (1), not_delivered_site_issue (2), delivered (3, also 'collected'), partially (4), not_delivered_ |
| detail | string | no | summary (default): key fields per order. full: every field Track-POD returns (goods lines, custom fields, photo links). |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Items per page (default 25, max 100). |
List the orders on one route, in route order, by route code (GET /Order/Route/Code/{code}). Paged here (offset/limit).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route_code | string | yes | The route code/number, e.g. R-1023. |
| status | array | no | Keep only orders with these delivery statuses: no_status (not yet attempted / unassigned), in_progress (1), not_delivered_site_issue (2), delivered (3, also 'collected'), partially (4), not_delivered_ |
| detail | string | no | summary (default): key fields per order. full: every field Track-POD returns (goods lines, custom fields, photo links). |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Items per page (default 25, max 100). |
Get one order with every field: client, address, time slot, goods lines, route, driver, delivery status, ETA, signature/photo links and tracking link. Pass exactly one of number, order_id or track_id (GET /Order/Number|Id|TrackId/{…}). A removed order answers with who removed it (HTTP 410).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | no | The order number (Order/Invoice/Job/Waybill number), e.g. cv30001-2. |
| order_id | string | no | The order Id — the unique identifier from your accounting system that the order was created with. |
| track_id | string | no | The order TrackId (UUID) from a tracking link or a webhook. |
List the last 25 orders that share one order number (re-deliveries, repeated jobs) — GET /Order/Number/{number}/List. Use it when an order number was reused and trackpod_get_order returns only one of them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | yes | The order number. |
| detail | string | no | summary (default): key fields per order. full: every field Track-POD returns (goods lines, custom fields, photo links). |
Get the electronic proof of delivery (ePOD) of one order: status and status time/GPS, who signed, signature and photo links (valid 24 h), driver comment, reject reasons, delivered vs ordered goods quantities, cash collected, customer feedback and the PDF delivery-note link (ReportUrl, valid 1 h). Pass exactly one of number, order_id or track_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | no | The order number (Order/Invoice/Job/Waybill number), e.g. cv30001-2. |
| order_id | string | no | The order Id — the unique identifier from your accounting system that the order was created with. |
| track_id | string | no | The order TrackId (UUID) from a tracking link or a webhook. |
List the account's reasons for not delivering / not collecting: site, order, goods and scanning issues (GET /RejectReason).
No parameter schema on file.
List the routes of one day (GET /Route/Date/{date}): code, status (Draft, Ready, Loaded, InProgress, Closed), driver, vehicle, planned vs actual start/finish, distance, cost, current GPS position, and per-route order counts by status. Paged here (offset/limit).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | The route date, YYYY-MM-DD. |
| status | array | no | Keep only routes with these statuses. |
| include_orders | string | no | none (default): order counts only. summary: key fields of each order. full: every order field (large). |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Items per page (default 25, max 100). |
Get one route with its status, driver, vehicle, timings, distance, cost, current GPS position and its orders. Pass exactly one of route_code or route_id (GET /Route/Code|Id/{…}).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route_code | string | no | The route code/number. |
| route_id | string | no | The route Id from your accounting system. |
| include_orders | string | no | summary (default): key fields of each order. none: counts only. full: every order field. |
Get the driver's recorded GPS track of a route (latitude, longitude, speed in m/s, time) — GET /Route/Track/Code|Id/{…}. Pass exactly one of route_code or route_id. Points are paged here (offset/limit, max 1000 per call).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route_code | string | no | The route code/number. |
| route_id | string | no | The route Id from your accounting system. |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Points per page (default 200, max 1000). |
List the account's drivers: name, username, phone, vehicle, depot, zone, teams and active flag (GET /Driver). Paged here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| active_only | boolean | no | Only active drivers (default false = all). |
| search | string | no | Keep only drivers whose name, username, phone or vehicle contains this text. |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Items per page (default 25, max 100). |
Get one driver by Track-POD id (UUID) or by username (GET /Driver/Id/{id} or /Driver/Username/{username}). Pass exactly one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| driver_id | string | no | The driver's Track-POD id (UUID, from trackpod_list_drivers). |
| username | string | no | The driver's username (login). |
List the account's vehicles: plate number, assigned driver, depot, capacity (weight/volume/pallets/size), limits, costs, type and carrier (GET /Vehicle, optional plate-number filter). Paged here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | no | Filter by vehicle (plate) number. |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Items per page (default 25, max 100). |
Get one vehicle by its Track-POD id (an integer, from trackpod_list_vehicles) — GET /Vehicle/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vehicle_id | integer | yes | The vehicle's Track-POD id. |
Driver vehicle inspections (before/after route): checklist items with pass/fail, notes, photo links (valid 24 h), odometer and signature. date only: every check of that day (GET /VehicleCheck/Date/{date}); date + vehicle_number: that vehicle's checks of the day; vehicle_number only: that vehicle's last check (GET /VehicleCheck/{number}).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | The day, YYYY-MM-DD. |
| vehicle_number | string | no | The vehicle (plate) number. |
| offset | integer | no | Items to skip (default 0). Use next_offset from the previous page. |
| limit | integer | no | Items per page (default 25, max 100). |
Create ONE REAL unscheduled order in Track-POD (POST /Order): a delivery or a collection for a client at an address, ready to be planned into a route by a dispatcher. It does not create or optimise routes. Depending on the account's notification settings the customer may later receive SMS/e-mail updates about it. Confirm the details with the user first. Address and client are required; Track-POD g
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | yes | The order number (your Order/Invoice/Job/Waybill number) — used later to look the order up, so no slash or backslash. |
| client | string | yes | Client/customer name. |
| address | string | yes | Delivery (or pickup) address, e.g. '2 St Josephs Crescent, Liverpool L3 3JF'. |
| type | string | no | delivery (default) or collection. |
| date | string | no | Order date, YYYY-MM-DD. |
| order_id | string | no | Your accounting-system id for the order. |
| depot | string | no | Depot address (else the account's default depot). |
| shipper | string | no | Shipper/supplier name. |
| address_lat | number | no | Address latitude (pass with address_lon to skip geocoding). |
| address_lon | number | no | Address longitude. |
| address_zone | string | no | Address zone. |
| time_slot_from | string | no | Desired delivery/pickup window start, local 24-hour time HH:mm. |
| time_slot_to | string | no | Desired delivery/pickup window end, local 24-hour time HH:mm. |
| service_time_minutes | number | no | Service time at the stop, minutes. |
| note | string | no | Note for the driver. |
| contact_name | string | no | Customer contact name. |
| phone | string | no | Customer contact phone. |
| string | no | Customer e-mail. | |
| weight | number | no | Total weight. |
| volume | number | no | Total volume. |
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 Track-POD 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 Track-POD 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.