Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
TrackingMore 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.
What it does
Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http trackingmore-mcp-by-usefulapi https://trackingmore.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# trackingmore_list_couriers, trackingmore_detect_courier, trackingmore_list_trackings and 4 more
TrackingMore 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.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 trackingmore-mcp-by-usefulapi https://trackingmore.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
7 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 carriers TrackingMore supports with their courier_code, name, country, website, phone and the extra fields some of them need. The full list is long (1,000+), so filter with search (matches name or code) and/or country; replies hold at most limit couriers. GET /couriers/all.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Case-insensitive text in the courier name or code, e.g. 'dhl'. |
| country | string | no | Courier country, ISO 3166 alpha-2, e.g. US. |
| limit | integer | no | Most couriers returned, 1-200 (default 50). |
| offset | integer | no | Skip this many matches (paging; default 0). |
Find which couriers a tracking number most likely belongs to (returns matching courier codes and names). Use the code with trackingmore_create_tracking. Does not create anything. POST /couriers/detect.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tracking_number | string | yes | The shipment's tracking number. |
List the shipments already registered in the TrackingMore account, newest first as the API returns them: id, tracking number, courier, delivery_status (pending, notfound, transit, pickup, delivered, undelivered, exception, expired, inforeceived), latest event and milestone dates. Checkpoint lists are left out (use trackingmore_get_tracking for one shipment's full history). Filters: tracking number
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tracking_numbers | string | no | One to 40 tracking numbers, comma-separated (TrackingMore refuses more than 40 per call). |
| courier_code | string | no | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). |
| delivery_status | string | no | pending, notfound, transit, pickup, delivered, undelivered, exception, expired or inforeceived. |
| archived_status | string | no | Archive filter: true = archived trackings, tracking = trackings that are not archived. |
| created_date_min | string | no | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
| created_date_max | string | no | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
| updated_date_min | string | no | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
| updated_date_max | string | no | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
| lang | string | no | Language for status text, e.g. en. |
| page | integer | no | Page number, from 1 (default 1). Sent as pages_amount. |
| limit | integer | no | Trackings per page, 1-200 (default 40). Sent as items_amount. |
The full tracking record of one shipment already registered in the account, including every checkpoint (origin_info / destination_info trackinfo with date, status, details and location). Look it up by tracking number; add courier_code if the number is used by several couriers. A number that was never registered is not found: register it with trackingmore_create_tracking first. GET /trackings/get?t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tracking_number | string | yes | The shipment's tracking number. |
| courier_code | string | no | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). |
| lang | string | no | Language for status text, e.g. en. |
WRITE: register ONE shipment so TrackingMore starts tracking it. This uses one credit of the account's plan (credits beyond the plan are billed by TrackingMore as overage): confirm with the user before creating, and never create trackings in bulk. Fails with 'Tracking No. already exists' if it is already registered. Needs the tracking number and the courier code (use trackingmore_detect_courier if
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tracking_number | string | yes | The shipment's tracking number. |
| courier_code | string | yes | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). |
| order_number | string | no | Your order number for this shipment. |
| order_id | string | no | Your order id in the shop system. |
| order_date | string | no | Order date, e.g. 2026-10-01T10:00:00+00:00. |
| title | string | no | Short title for the shipment. |
| customer_name | string | no | Recipient name. |
| customer_email | string | no | Recipient email (TrackingMore can send delivery notifications to it when enabled in the account). |
| customer_sms | string | no | Recipient mobile number, with country code. |
| note | string | no | Free-text note. |
| label | string | no | Label to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131). |
| language | string | no | Language code for status text, e.g. en. |
| logistics_channel | string | no | Logistics channel / service name. |
| origin_country_iso2 | string | no | Origin country, ISO 3166 alpha-2. |
| destination_country_iso2 | string | no | Destination country, ISO 3166 alpha-2. |
| tracking_origin_country | string | no | Origin country for couriers that need it, ISO 3166 alpha-2. |
| tracking_destination_country | string | no | Destination country for couriers that need it, ISO 3166 alpha-2. |
| tracking_postal_code | string | no | Recipient postal code (needed by some couriers). |
| tracking_ship_date | string | no | Ship date, yyyymmdd (needed by some couriers). |
| tracking_courier_account | string | no | Courier account (needed by some couriers). |
WRITE: change the descriptive fields of a registered tracking (order number, customer name/email, title, note, label, language, postal code, ship date ...). Only the fields you pass change; the tracking number and courier cannot be changed here. PUT /trackings/update/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | TrackingMore tracking id (the id field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking). |
| order_number | string | no | Your order number for this shipment. |
| order_id | string | no | Your order id in the shop system. |
| order_date | string | no | Order date, e.g. 2026-10-01T10:00:00+00:00. |
| title | string | no | Short title for the shipment. |
| customer_name | string | no | Recipient name. |
| customer_email | string | no | Recipient email (TrackingMore can send delivery notifications to it when enabled in the account). |
| customer_sms | string | no | Recipient mobile number, with country code. |
| note | string | no | Free-text note. |
| label | string | no | Label to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131). |
| language | string | no | Language code for status text, e.g. en. |
| logistics_channel | string | no | Logistics channel / service name. |
| origin_country_iso2 | string | no | Origin country, ISO 3166 alpha-2. |
| destination_country_iso2 | string | no | Destination country, ISO 3166 alpha-2. |
| tracking_origin_country | string | no | Origin country for couriers that need it, ISO 3166 alpha-2. |
| tracking_destination_country | string | no | Destination country for couriers that need it, ISO 3166 alpha-2. |
| tracking_postal_code | string | no | Recipient postal code (needed by some couriers). |
| tracking_ship_date | string | no | Ship date, yyyymmdd (needed by some couriers). |
| tracking_courier_account | string | no | Courier account (needed by some couriers). |
| tracking_key | string | no | Tracking key / phone suffix (needed by some couriers). |
WRITE (destructive): permanently remove one tracking from the TrackingMore account by id. Its checkpoint history is lost; registering the shipment again later uses another credit. Confirm with the user first. DELETE /trackings/delete/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | TrackingMore tracking id (the id field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking). |
- 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 TrackingMore MCP by usefulapi or to call it, at any volume.
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.
No release note was published with this version.
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.
Any signed-in account that does not publish TrackingMore 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.
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.