TrackingMore MCP by usefulapi
Server Details
Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Score is being calculated.
Available Tools
7 toolstrackingmore_create_trackingRegister a shipment for trackingDestructiveInspect
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 unknown). Some couriers need extra fields (postal code, ship date, key). Returns the new tracking with its id. POST /trackings/create.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Free-text note. | |
| label | No | Label to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131). | |
| title | No | Short title for the shipment. | |
| language | No | Language code for status text, e.g. en. | |
| order_id | No | Your order id in the shop system. | |
| order_date | No | Order date, e.g. 2026-10-01T10:00:00+00:00. | |
| courier_code | Yes | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). | |
| customer_sms | No | Recipient mobile number, with country code. | |
| order_number | No | Your order number for this shipment. | |
| tracking_key | No | Tracking key / phone suffix (needed by some couriers). | |
| customer_name | No | Recipient name. | |
| customer_email | No | Recipient email (TrackingMore can send delivery notifications to it when enabled in the account). | |
| tracking_number | Yes | The shipment's tracking number. | |
| logistics_channel | No | Logistics channel / service name. | |
| recipient_postcode | No | Recipient postcode. | |
| tracking_ship_date | No | Ship date, yyyymmdd (needed by some couriers). | |
| origin_country_iso2 | No | Origin country, ISO 3166 alpha-2. | |
| tracking_postal_code | No | Recipient postal code (needed by some couriers). | |
| tracking_origin_country | No | Origin country for couriers that need it, ISO 3166 alpha-2. | |
| destination_country_iso2 | No | Destination country, ISO 3166 alpha-2. | |
| tracking_courier_account | No | Courier account (needed by some couriers). | |
| tracking_destination_country | No | Destination country for couriers that need it, ISO 3166 alpha-2. |
trackingmore_delete_trackingDelete a trackingDestructiveIdempotentInspect
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}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | TrackingMore tracking id (the `id` field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking). |
trackingmore_detect_courierDetect courier from a tracking numberRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| tracking_number | Yes | The shipment's tracking number. |
trackingmore_get_trackingGet a shipment's trackingRead-onlyInspect
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?tracking_numbers=.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language for status text, e.g. en. | |
| courier_code | No | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). | |
| tracking_number | Yes | The shipment's tracking number. |
trackingmore_list_couriersList supported couriersRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Most couriers returned, 1-200 (default 50). | |
| offset | No | Skip this many matches (paging; default 0). | |
| search | No | Case-insensitive text in the courier name or code, e.g. 'dhl'. | |
| country | No | Courier country, ISO 3166 alpha-2, e.g. US. |
trackingmore_list_trackingsList trackingsRead-onlyInspect
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 numbers, courier, delivery status, created/updated date range. GET /trackings/get.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language for status text, e.g. en. | |
| page | No | Page number, from 1 (default 1). Sent as pages_amount. | |
| limit | No | Trackings per page, 1-200 (default 40). Sent as items_amount. | |
| courier_code | No | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). | |
| archived_status | No | Archive filter: true = archived trackings, tracking = trackings that are not archived. | |
| delivery_status | No | pending, notfound, transit, pickup, delivered, undelivered, exception, expired or inforeceived. | |
| created_date_max | 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_min | 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. | |
| tracking_numbers | No | One to 40 tracking numbers, comma-separated (TrackingMore refuses more than 40 per call). | |
| updated_date_max | 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 | 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. |
trackingmore_update_trackingUpdate a tracking's detailsDestructiveIdempotentInspect
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}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | TrackingMore tracking id (the `id` field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking). | |
| note | No | Free-text note. | |
| label | No | Label to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131). | |
| title | No | Short title for the shipment. | |
| language | No | Language code for status text, e.g. en. | |
| order_id | No | Your order id in the shop system. | |
| order_date | No | Order date, e.g. 2026-10-01T10:00:00+00:00. | |
| customer_sms | No | Recipient mobile number, with country code. | |
| order_number | No | Your order number for this shipment. | |
| tracking_key | No | Tracking key / phone suffix (needed by some couriers). | |
| customer_name | No | Recipient name. | |
| customer_email | No | Recipient email (TrackingMore can send delivery notifications to it when enabled in the account). | |
| logistics_channel | No | Logistics channel / service name. | |
| recipient_postcode | No | Recipient postcode. | |
| tracking_ship_date | No | Ship date, yyyymmdd (needed by some couriers). | |
| origin_country_iso2 | No | Origin country, ISO 3166 alpha-2. | |
| tracking_postal_code | No | Recipient postal code (needed by some couriers). | |
| tracking_origin_country | No | Origin country for couriers that need it, ISO 3166 alpha-2. | |
| destination_country_iso2 | No | Destination country, ISO 3166 alpha-2. | |
| tracking_courier_account | No | Courier account (needed by some couriers). | |
| tracking_destination_country | No | Destination country for couriers that need it, ISO 3166 alpha-2. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
7 tool updates
- First observed
trackingmore_create_tracking - First observed
trackingmore_delete_tracking - First observed
trackingmore_detect_courier - First observed
trackingmore_get_tracking - First observed
trackingmore_list_couriers - First observed
trackingmore_list_trackings - First observed
trackingmore_update_tracking
Related MCP Connectors
Track parcels across 2,500+ carriers and 3PLs: live delivery status, event history, carrier lookup.
Auto-detect carrier from tracking number: USPS, UPS, FedEx, DHL, India Post, more.
Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates.
Track parcels across 3000+ carriers with 17TRACK: register numbers, read tracking events and quota.
91
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceTrack packages across 3,200+ carriers (USPS, UPS, FedEx, DHL, China Post, UniUni, SpeedX and more) with automatic carrier detection. Register, list, and archive tracking numbers and get real-time delivery event timelines via the 24hTrack API.57 npmMIT
- AlicenseBqualityDmaintenanceAllows tracking of parcel deliveries across various carriers using the 17track.net API, with automatic or manual carrier detection.214 npm6MIT
- FlicenseNot gradedqualityDmaintenanceEnables package tracking across multiple carriers by auto-detecting the carrier from a tracking number and returning structured events. Supports USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart, and Aramex.-

Trackmage MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceProvides shipment tracking api and logistics management capabilities through the TrackMage API. Enables creation and monitoring of shipments and orders, carrier detection, tracking checkpoint retrieval, and comprehensive logistics workflow automation.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.