Is ModelCostComparison down?

MCP serverBy modelcostcomparison.com. How to connect and its trust score are on the listing page.

Up

No, ModelCostComparison is up.

It passed its latest check 2 h ago in 373 ms. It has passed every check since 27 Oct 2026, 12:47 UTC.

Latest check

Last check
2 h ago (6 Nov 2026, 21:44 UTC)
Response time
373 ms (typical 417 ms)
Next check
In about 11 h
How often
About every 14 hours over the last 7 days

Uptime

Last 24 hours100%2 checks
Last 7 days100%13 checks
Last 30 days78.7%47 checks
All checks passedSome failedAll failedNot checked

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

Outages in the last 30 days

2 outages, 8 days 21 h of failed checks in total, the longest 6 days 17 h.

StartedDurationFailed checksFirst error
20 Oct 2026, 19:57 UTC6 days 17 h7initialize returned HTTP 503
17 Oct 2026, 20:39 UTC2 days 4 h3initialize returned HTTP 503

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

Recent checks

WhenResultHTTPTime
6 Nov 2026, 21:44 UTCPassed200373 ms
6 Nov 2026, 11:37 UTCPassed200363 ms
5 Nov 2026, 22:51 UTCPassed200396 ms
5 Nov 2026, 07:54 UTCPassed200417 ms
4 Nov 2026, 17:32 UTCPassed200847 ms
4 Nov 2026, 02:53 UTCPassed200417 ms
3 Nov 2026, 12:44 UTCPassed200395 ms
2 Nov 2026, 22:18 UTCPassed200607 ms
2 Nov 2026, 08:52 UTCPassed200765 ms
1 Nov 2026, 21:57 UTCPassed2001.0 s

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 14 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.