Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Track international packages by tracking number. Supports 3100+ carriers (China Post, DHL, FedEx, UPS, USPS, Yanwen, Cainiao, etc.) via 17track. Optional: se...
Track international packages by tracking number. Supports 3100+ carriers (China Post, DHL, FedEx, UPS, USPS, Yanwen, Cainiao, etc.) via 17track. Optional: se...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Track international packages by tracking number only. Supports 3100+ carriers worldwide.
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
ModeAPI Key Required?DescriptionWith TRACK17_API_KEYYes (1 key)Uses the official api.17track.net — most reliable, 3100+ carriers.Without keyNoUses Playwright (headless Chromium) to query t.17track.net. Requires playwright npm package. Recommendation: Set TRACK17_API_KEY for the best reliability. Get a free key at https://api.17track.net
You deploy the MCP HTTP server with TRACK17_API_KEY on your server. End users connect via URL — they don't need any API key.
export TRACK17_API_KEY=your-17track-api-key npx -y @shopmeagent/logistics-tracking-mcp serve # Default: http://0.0.0.0:3000/mcp # Override with PORT and HOST env vars
{ "mcpServers": { "logistics-tracking": { "type": "streamable-http", "url": "https://your-domain.com/mcp" } } } Users only need a tracking number — no API key required on their end.
Zero-config (no key, uses Playwright fallback — requires playwright installed): { "mcpServers": { "logistics-tracking": { "command": "npx", "args": ["-y", "@shopmeagent/logistics-tracking-mcp"] } } } Recommended — with API key for broader carrier coverage and better reliability: { "mcpServers": { "logistics-tracking": { "command": "npx", "args": ["-y", "@shopmeagent/logistics-tracking-mcp"], "env": { "TRACK17_API_KEY": "your-17track-api-key" } } } } Get a free 17track API key: https://api.17track.net
Add this skill to OpenClaw: npx skills add shopmeskills/mcp Then in OpenClaw's MCP configuration, add either the HTTP or stdio config shown above. Example prompts: "Track package YT2412345678901234" "Where is my package LX123456789CN?" "Check status of 1ZABCDEF1234567890"
Query tracking info for a single package. Input: trackingNumber (required), carrier (optional, auto-detected) Returns: status, current location, timeline of events
Identify the carrier from a tracking number's format. Input: trackingNumber Returns: carrier name, confidence level
Track up to 40 packages at once. Input: trackingNumbers array Returns: array of tracking results
Get a human-readable explanation of a tracking status code. Input: statusCode (e.g. InTransit, CustomsClearance, Delivered) Returns: description and advice in English
PatternCarrierExampleXX123456789CNChina PostLX123456789CNEX123456789CNChina EMSEA123456789CNYT + 16 digitsYanwenYT1234567890123456LP + 14+ digitsCainiaoLP12345678901234SF + 12+ digitsSF ExpressSF12345678901231Z + 16 charsUPS1ZABCDEF123456789094/93/92 + 20 digitsUSPS940011189922310001234510-11 digitsDHL123456789012-15 digitsFedEx123456789012
RouteStandardExpressChina to US15-30 days5-10 daysChina to EU15-30 days5-10 daysChina to SE Asia7-15 days3-7 daysChina to Japan/Korea5-10 days3-5 days
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
No key needed: Without TRACK17_API_KEY, the tool uses Playwright to query 17track directly. Install Playwright with npm install playwright for this to work. 3100+ carriers: With a 17track API key, auto-detects carrier from the tracking number. Wait 24-48 hours after shipment before tracking — data may not be available on day one. Allow at least 2 hours between queries for the same tracking number to avoid rate limiting. Use batch_track for multiple packages — more efficient than individual queries.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.