Skip to main content
Glama

TrackingMore MCP by usefulapi

Server Details

Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
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 tools
trackingmore_create_trackingRegister a shipment for tracking
Destructive
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
noteNoFree-text note.
labelNoLabel to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131).
titleNoShort title for the shipment.
languageNoLanguage code for status text, e.g. en.
order_idNoYour order id in the shop system.
order_dateNoOrder date, e.g. 2026-10-01T10:00:00+00:00.
courier_codeYesTrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier).
customer_smsNoRecipient mobile number, with country code.
order_numberNoYour order number for this shipment.
tracking_keyNoTracking key / phone suffix (needed by some couriers).
customer_nameNoRecipient name.
customer_emailNoRecipient email (TrackingMore can send delivery notifications to it when enabled in the account).
tracking_numberYesThe shipment's tracking number.
logistics_channelNoLogistics channel / service name.
recipient_postcodeNoRecipient postcode.
tracking_ship_dateNoShip date, yyyymmdd (needed by some couriers).
origin_country_iso2NoOrigin country, ISO 3166 alpha-2.
tracking_postal_codeNoRecipient postal code (needed by some couriers).
tracking_origin_countryNoOrigin country for couriers that need it, ISO 3166 alpha-2.
destination_country_iso2NoDestination country, ISO 3166 alpha-2.
tracking_courier_accountNoCourier account (needed by some couriers).
tracking_destination_countryNoDestination country for couriers that need it, ISO 3166 alpha-2.
trackingmore_delete_trackingDelete a tracking
DestructiveIdempotent
Inspect

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}.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesTrackingMore tracking id (the `id` field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking).
trackingmore_detect_courierDetect courier from a tracking number
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
tracking_numberYesThe shipment's tracking number.
trackingmore_get_trackingGet a shipment's tracking
Read-only
Inspect

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=.

ParametersJSON Schema
NameRequiredDescriptionDefault
langNoLanguage for status text, e.g. en.
courier_codeNoTrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier).
tracking_numberYesThe shipment's tracking number.
trackingmore_list_couriersList supported couriers
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMost couriers returned, 1-200 (default 50).
offsetNoSkip this many matches (paging; default 0).
searchNoCase-insensitive text in the courier name or code, e.g. 'dhl'.
countryNoCourier country, ISO 3166 alpha-2, e.g. US.
trackingmore_list_trackingsList trackings
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
langNoLanguage for status text, e.g. en.
pageNoPage number, from 1 (default 1). Sent as pages_amount.
limitNoTrackings per page, 1-200 (default 40). Sent as items_amount.
courier_codeNoTrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier).
archived_statusNoArchive filter: true = archived trackings, tracking = trackings that are not archived.
delivery_statusNopending, notfound, transit, pickup, delivered, undelivered, exception, expired or inforeceived.
created_date_maxNoA 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_minNoA 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_numbersNoOne to 40 tracking numbers, comma-separated (TrackingMore refuses more than 40 per call).
updated_date_maxNoA 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_minNoA 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 details
DestructiveIdempotent
Inspect

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}.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesTrackingMore tracking id (the `id` field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking).
noteNoFree-text note.
labelNoLabel to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131).
titleNoShort title for the shipment.
languageNoLanguage code for status text, e.g. en.
order_idNoYour order id in the shop system.
order_dateNoOrder date, e.g. 2026-10-01T10:00:00+00:00.
customer_smsNoRecipient mobile number, with country code.
order_numberNoYour order number for this shipment.
tracking_keyNoTracking key / phone suffix (needed by some couriers).
customer_nameNoRecipient name.
customer_emailNoRecipient email (TrackingMore can send delivery notifications to it when enabled in the account).
logistics_channelNoLogistics channel / service name.
recipient_postcodeNoRecipient postcode.
tracking_ship_dateNoShip date, yyyymmdd (needed by some couriers).
origin_country_iso2NoOrigin country, ISO 3166 alpha-2.
tracking_postal_codeNoRecipient postal code (needed by some couriers).
tracking_origin_countryNoOrigin country for couriers that need it, ISO 3166 alpha-2.
destination_country_iso2NoDestination country, ISO 3166 alpha-2.
tracking_courier_accountNoCourier account (needed by some couriers).
tracking_destination_countryNoDestination 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.

  1. 7 tool updates
    • First observedtrackingmore_create_tracking
    • First observedtrackingmore_delete_tracking
    • First observedtrackingmore_detect_courier
    • First observedtrackingmore_get_tracking
    • First observedtrackingmore_list_couriers
    • First observedtrackingmore_list_trackings
    • First observedtrackingmore_update_tracking

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Track 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 npm
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    Allows tracking of parcel deliveries across various carriers using the 17track.net API, with automatic or manual carrier detection.
    2
    14 npm
    6
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides 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.
    2
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.