Is ClaimHit down?

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

Down

Yes, ClaimHit is down.

It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 308.

Latest check

Last check
25 h ago (26 Oct 2026, 23:21 UTC)
Response time
Not measured
Next check
In about 47 h
How often
About every 3 days over the last 7 days

Uptime

Last 24 hours-0 checks
Last 7 days0.0%2 checks
Last 30 days0.0%12 checks
All checks passedSome failedAll failedNot checked

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

Outages in the last 30 days

No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.

Recent checks

WhenResultHTTPTime
26 Oct 2026, 23:21 UTCinitialize returned HTTP 308308141 ms
23 Oct 2026, 23:25 UTCinitialize returned HTTP 308308261 ms
20 Oct 2026, 19:29 UTCinitialize returned HTTP 308308136 ms
19 Oct 2026, 15:37 UTCinitialize returned HTTP 308308203 ms
18 Oct 2026, 12:18 UTCinitialize returned HTTP 308308214 ms
17 Oct 2026, 07:50 UTCinitialize returned HTTP 308308106 ms
16 Oct 2026, 03:19 UTCinitialize returned HTTP 308308230 ms
14 Oct 2026, 21:15 UTCinitialize returned HTTP 308308338 ms
13 Oct 2026, 17:13 UTCinitialize returned HTTP 308308204 ms
12 Oct 2026, 13:59 UTCinitialize returned HTTP 308308165 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 3 days 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.