TrackingMore MCP by usefulapi
io.usefulapi/trackingmore · v1.0.0
Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.
MCPremoteno credentialsAnalytics & marketing
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 7 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 7 tools · 4 read, 3 write (incl. delete/pay) · Analytics & marketing, Developer tools
Test call trackingmore_list_couriers: needs a key: HTTP 401 (1,032 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://trackingmore.usefulapi.io/mcpTools
7 tools listed at last check
trackingmore_list_couriersList 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.trackingmore_detect_courierFind 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.trackingmore_list_trackingsList 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 artrackingmore_get_trackingThe 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 nevetrackingmore_create_trackingWRITE: 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 altrackingmore_update_trackingWRITE: 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}.trackingmore_delete_trackingWRITE (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}.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.usefulapi/trackingmore)