https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp ↗
Multi-Carrier Tracking is a remote MCP server published at multi-carrier-tracking-mcp.atlasword.workers.dev. It has been probed 34 times since 9/4/2026. It answered in 34 of them (100.0%), a near-uninterrupted record. Median response time is 228 ms, placing it among the faster endpoints. Its tool list could not be read; the server is closed to direct calls.
Auto-detect carrier from tracking number: USPS, UPS, FedEx, DHL, India Post, more.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
track_multiple — Missing explicit input schema for batch tracking parameters| Run | Era | Modern | ms | Legacy | ms |
|---|
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-guptaprakhariitr-multi-carrier-tracking-mcp)<a href="https://mcpmetrics.io/servers/io-github-guptaprakhariitr-multi-carrier-tracking-mcp"><img src="https://mcpmetrics.io/badge/io.github.guptaprakhariitr/multi-carrier-tracking-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Versions |
|---|
| 2026-09-07 05:25:31 | Unknown | 500 | 210 | 500 | 208 | — |
| 2026-09-07 02:57:58 | Unknown | 500 | 127 | 500 | 125 | — |
| 2026-09-07 00:27:42 | Legacy | 200 | 207 | 200 | 212 | 2025-06-18 |
| 2026-09-06 22:36:06 | Unknown | 500 | 194 | 500 | 188 | — |
| 2026-09-06 20:44:13 | Unknown | 500 | 228 | 500 | 226 | — |
| 2026-09-06 18:49:47 | Unknown | 500 | 266 | 500 | 260 | — |
| 2026-09-06 16:56:18 | Unknown | 500 | 245 | 500 | 248 | — |
| 2026-09-06 15:42:25 | Unknown | 500 | 191 | 500 | 187 | — |
| 2026-09-06 13:49:02 | Unknown | 500 | 259 | 500 | 196 | — |
| 2026-09-06 11:55:12 | Unknown | 500 | 199 | 500 | 197 | — |
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.