mcpbeat

cloud_dj MCP Server

live.alpic.clouddj-ce0f8cfd/clouddj
answering

cloud_dj is answering right now. Last checked 10 min ago.

cloud_dj

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
362 ms
Response time
average over 24h
open, no key
Access
sse

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add clouddj --transport http https://clouddj-ce0f8cfd.alpic.live
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "clouddj": {
      "url": "https://clouddj-ce0f8cfd.alpic.live"
    }
  }
}
~/.codex/config.toml
[mcp_servers.clouddj]
url = "https://clouddj-ce0f8cfd.alpic.live"
.cursor/mcp.json
{
  "mcpServers": {
    "clouddj": {
      "url": "https://clouddj-ce0f8cfd.alpic.live"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "clouddj": {
      "url": "https://clouddj-ce0f8cfd.alpic.live"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://clouddj-ce0f8cfd.alpic.live sse answering 304 ms 10 min ago

cloud_dj — questions

Answers built from our own checks of this server.

Is cloud_dj working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 362 ms. The bar chart above shows every period we have measured.
How do I connect cloud_dj?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does cloud_dj need an API key?
No. cloud_dj completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is cloud_dj?
It answers our handshake in 362 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.