Is DiscoverLaunches down?

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

Possible problem

DiscoverLaunches may be having problems.

Its latest check failed 1 min ago: Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR). The check before passed. Two failed checks in a row count as an outage. Next check: not before 8 Nov 2026, 01:20 UTC.

Latest check

Last check
1 min ago (7 Nov 2026, 19:16 UTC)
Response time
Not measured (typical 481 ms)
Next check
Not before 8 Nov 2026, 01:20 UTC
How often
About every 14 hours over the last 7 days

Uptime

Last 24 hours66.7%3 checks
Last 7 days92.3%13 checks
Last 30 days92.9%14 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

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
7 Nov 2026, 19:16 UTCConnection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR)--
7 Nov 2026, 07:05 UTCPassed200500 ms
6 Nov 2026, 19:58 UTCPassed200488 ms
6 Nov 2026, 08:47 UTCPassed200626 ms
5 Nov 2026, 19:04 UTCPassed200495 ms
5 Nov 2026, 03:41 UTCPassed200481 ms
4 Nov 2026, 12:42 UTCPassed200476 ms
3 Nov 2026, 21:39 UTCPassed40264 ms
3 Nov 2026, 07:36 UTCPassed200221 ms
2 Nov 2026, 17:25 UTCPassed2001.2 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.