International Logistics Tracking

Track packages across borders with carrier auto-detection and status explanation.

When to Use

• User asks “where is my package” or provides a tracking number
• User needs to check shipment status or delivery estimate
• User asks about customs clearance or logistics exceptions
• User needs to track multiple packages at once

MCP Server Setup

This skill works best with the companion MCP server. Add to your MCP config:

{
  "mcpServers": {
    "logistics-tracking": {
      "command": "npx",
      "args": ["-y", "@shopme/logistics-tracking-mcp"],
      "env": {
        "TRACK17_API_KEY": "your-17track-api-key"
      }
    }
  }
}

Get a free 17track API key at https://api.17track.net

Available Tools

track_package

Query tracking info for a single package.

• Input: trackingNumber (required), carrier (optional), language (en/zh)
• Returns: status, current location, timeline of events

detect_carrier

Identify the carrier from a tracking number’s format.

• Input: trackingNumber
• Returns: carrier name, confidence level

batch_track

Track up to 40 packages at once.

• Input: trackingNumbers array, language
• Returns: array of tracking results

explain_status

Get a human-readable explanation of a tracking status code.

• Input: statusCode (e.g. InTransit, CustomsClearance)
• Returns: English and Chinese explanation with advice

Tracking Number Format Guide

Typical Delivery Times (International)

Status Codes Explained

• InfoReceived: Carrier has the info but hasn’t picked up the package (1-3 day wait)
• InTransit: Package is moving through the logistics network
• CustomsClearance: Going through customs (3-7 business days typical)
• OutForDelivery: Final delivery attempt today
• Delivered: Successfully delivered
• Exception: Problem occurred (customs hold, wrong address, failed delivery)
• Returned: Being sent back to origin

Tips

1. If TRACK17_API_KEY is not set, the server falls back to RTB56 (limited accuracy)
2. For best results, wait 24-48 hours after shipping before first query
3. Query no more than once every 2 hours per tracking number to avoid rate limits
4. Batch tracking is more efficient for multiple packages