Is Time down?

MCP serverBy clockchain-time-rp6evdzqkq-uc.a.run.app. How to connect and its trust score are on the listing page.

Down

Yes, Time is down.

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

Latest check

Last check: 16 h ago (27 Oct 2026, 05:36 UTC)
Response time: Not measured
Next check: In about 2 days
How often: About every 3 days over the last 7 days

Uptime

Last 24 hours0.0%1 check

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

When	Result	HTTP	Time
27 Oct 2026, 05:36 UTC	initialize returned HTTP 500	500	220 ms
24 Oct 2026, 03:29 UTC	initialize returned HTTP 500	500	228 ms
20 Oct 2026, 17:51 UTC	initialize returned HTTP 503	503	212 ms
19 Oct 2026, 13:52 UTC	initialize returned HTTP 500	500	218 ms
18 Oct 2026, 10:57 UTC	initialize returned HTTP 500	500	250 ms
17 Oct 2026, 05:17 UTC	initialize returned HTTP 500	500	400 ms
15 Oct 2026, 23:43 UTC	initialize returned HTTP 500	500	233 ms
14 Oct 2026, 19:23 UTC	initialize returned HTTP 500	500	258 ms
13 Oct 2026, 17:43 UTC	initialize returned HTTP 500	500	206 ms
12 Oct 2026, 15:53 UTC	initialize returned HTTP 500	500	239 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.