Is Verify down?

MCP serverBy zaroniacalculator.co.za. How to connect and its trust score are on the listing page.

Down

Yes, Verify is down.

It has failed every check since 1 Nov 2026, 21:41 UTC (8 days 15 h, 9 checks). Latest error: Connection failed (ERR_TLS_CERT_ALTNAME_INVALID). It last passed on 1 Nov 2026, 12:13 UTC.

Latest check

Last check
6 h ago (10 Nov 2026, 07:06 UTC)
Response time
Not measured (typical 1.1 s)
Next check
In about 23 h
How often
About every 29 hours over the last 7 days

Uptime

Last 24 hours0.0%1 check
Last 7 days0.0%6 checks
Last 30 days82.1%56 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, 8 days 15 h of failed checks in total.

StartedDurationFailed checksFirst error
1 Nov 2026, 21:41 UTCOngoing, 8 days 15 h so far9Connection failed (ERR_TLS_CERT_ALTNAME_INVALID)

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

WhenResultHTTPTime
10 Nov 2026, 07:06 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
9 Nov 2026, 02:45 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
7 Nov 2026, 21:41 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
6 Nov 2026, 16:53 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
5 Nov 2026, 13:09 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
4 Nov 2026, 05:11 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
2 Nov 2026, 22:26 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
2 Nov 2026, 08:08 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
1 Nov 2026, 21:41 UTCConnection failed (ERR_TLS_CERT_ALTNAME_INVALID)--
1 Nov 2026, 12:13 UTCPassed2001.1 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 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.