Is cloud_dj down?

MCP serverBy clouddj-ce0f8cfd.alpic.live. How to connect and its trust score are on the listing page.

Down

Yes, cloud_dj is down.

It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}.

Latest check

Last check
3 h ago (18 Oct 2026, 07:51 UTC)
Response time
Not measured
Next check
In about 24 h
How often
About every 27 hours over the last 7 days

Uptime

Last 24 hours0.0%1 check
Last 7 days0.0%8 checks
Last 30 days0.0%8 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, 07:51 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200512 ms
17 Oct 2026, 04:00 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200541 ms
16 Oct 2026, 01:38 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200536 ms
14 Oct 2026, 22:45 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200494 ms
13 Oct 2026, 19:31 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200857 ms
12 Oct 2026, 16:17 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200477 ms
12 Oct 2026, 06:22 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200506 ms
11 Oct 2026, 20:16 UTCinitialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}200497 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.