Multi-Carrier Tracking
by multi-carrier-tracking-mcp.atlasword.workers.dev in Other
Auto-detect carrier from tracking number: USPS, UPS, FedEx, DHL, India Post, more.
https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp- Tools
- 4
- open to any client
- Uptime
- 6.3%
- last 30 days
- Response time
- 252 ms
- 252 ms slowest 5%
- Last check
- Failed
- 42 h ago, next in 24 h
Reliability
Latest check failed 42 h ago: initialize returned HTTP 500
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"multi-carrier-tracking": {
"type": "http",
"url": "https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp"
}
}
}4 tools
- track_package
Get the current status and event history for a single package. Auto-detects the carrier from the tracking number; pass `carrier` explicitly if detection is ambiguous. Returns structured events with timestamp, status, and location.
- track_multiple
Batch tracking. Provide up to 25 tracking numbers; auto-detects each carrier and returns results in the same order. Slower entries are not retried within the batch.
- detect_carrier
Identify which carrier a tracking number belongs to, without actually fetching status. Returns primary guess + any other candidates for ambiguous numbers.
- list_carriers
List supported carriers and their countries.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 42 h ago | initialize returned HTTP 500 | 500 | 214 ms |
| 3 days ago | initialize returned HTTP 500 | 500 | 278 ms |
| 4 days ago | initialize returned HTTP 500 | 500 | 202 ms |
| 5 days ago | initialize returned HTTP 500 | 500 | 171 ms |
| 7 days ago | initialize returned HTTP 500 | 500 | 196 ms |
Show 10 older checks
| 8 days ago | initialize returned HTTP 500 | 500 | 303 ms |
| 9 days ago | initialize returned HTTP 500 | 500 | 209 ms |
| 10 days ago | initialize returned HTTP 500 | 500 | 175 ms |
| 11 days ago | initialize returned HTTP 500 | 500 | 210 ms |
| 11 days ago | initialize returned HTTP 500 | 500 | 254 ms |
| 12 days ago | Passed | 200 | 252 ms |
| 13 days ago | initialize returned HTTP 500 | 500 | 271 ms |
| 14 days ago | initialize returned HTTP 500 | 500 | 290 ms |
| 15 days ago | initialize returned HTTP 500 | 500 | 265 ms |
| 15 days ago | initialize returned HTTP 500 | 500 | 160 ms |