Is Hourly Rate down?

MCP serverBy zovo.one. How to connect and its trust score are on the listing page.

Down

Yes, Hourly Rate is down.

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

Latest check

Last check
12 h ago (18 Oct 2026, 17:40 UTC)
Response time
Not measured
Next check
In about 15 h
How often
About every 27 hours over the last 7 days

Uptime

Last 24 hours0.0%1 check
Last 7 days0.0%6 checks
Last 30 days0.0%6 checks
All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 27 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
18 Oct 2026, 17:40 UTCinitialize returned HTTP 4044041.6 s
17 Oct 2026, 14:10 UTCinitialize returned HTTP 404404312 ms
16 Oct 2026, 11:12 UTCinitialize returned HTTP 4044041.3 s
15 Oct 2026, 06:22 UTCinitialize returned HTTP 404404529 ms
14 Oct 2026, 21:08 UTCinitialize returned HTTP 404404226 ms
14 Oct 2026, 10:48 UTCinitialize returned HTTP 404404949 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 27 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.