Is Multi-Carrier Tracking down?

MCP serverBy multi-carrier-tracking-mcp.atlasword.workers.dev. How to connect and its trust score are on the listing page.

Down

Yes, Multi-Carrier Tracking is down.

It has failed every check since 16 Oct 2026, 10:26 UTC (11 days 4 h, 10 checks). Latest error: initialize returned HTTP 500. It last passed on 16 Oct 2026, 00:40 UTC.

Latest check

Last check: 43 h ago (25 Oct 2026, 19:05 UTC)
Response time: Not measured (typical 252 ms)
Next check: In about 23 h
How often: About every 29 hours over the last 7 days

Uptime

Last 24 hours-0 checks

Last 7 days0.0%5 checks

Last 30 days6.3%16 checks

All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 29 hours over the last 7 days.

Outages in the last 30 days

1 outage, 11 days 4 h of failed checks in total.

Started	Duration	Failed checks	First error
16 Oct 2026, 10:26 UTC	Ongoing, 11 days 4 h so far	10	initialize returned HTTP 500

Times are when our checks ran, about every 29 hours for this listing, so start times and durations are accurate to about that.

Recent checks

When	Result	HTTP	Time
25 Oct 2026, 19:05 UTC	initialize returned HTTP 500	500	214 ms
24 Oct 2026, 13:56 UTC	initialize returned HTTP 500	500	278 ms
23 Oct 2026, 08:29 UTC	initialize returned HTTP 500	500	202 ms
22 Oct 2026, 03:05 UTC	initialize returned HTTP 500	500	171 ms
20 Oct 2026, 21:37 UTC	initialize returned HTTP 500	500	196 ms
19 Oct 2026, 16:03 UTC	initialize returned HTTP 500	500	303 ms
18 Oct 2026, 13:55 UTC	initialize returned HTTP 500	500	209 ms
17 Oct 2026, 07:37 UTC	initialize returned HTTP 500	500	175 ms
16 Oct 2026, 20:54 UTC	initialize returned HTTP 500	500	210 ms
16 Oct 2026, 10:26 UTC	initialize returned HTTP 500	500	254 ms

How we check

Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.

Checks come from our server, about every 29 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.

If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.