mcpbeat

Signal API MCP Server

live.bitcoinintel/signal-api
not responding

Signal API is listed as active in the registry but did not answer our last check.

Bitcoin 15-min prediction signals with on-chain commitment proofs. L402-gated.

Uptime history 42 hours of history · worst hour 0%
42 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
26 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 3 min ago.

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

Endpoints

URLTransportStateLatencyChecked
https://mcp.bitcoinintel.live/mcp/sse sse answering 26 ms 3 min ago

Signal API — questions

Answers built from our own checks of this server.

Is Signal API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 26 ms. The bar chart above shows every period we have measured.
The registry lists Signal API as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Signal API?
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 Signal API need an API key?
No. Signal API 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.