mcpbeat

channel-lab MCP Server

io.dedyn.studiolabsc/channel-lab
not responding

channel-lab is listed as active in the registry but did not answer our last check.

Studio distribution-lab reference MCP endpoint (channel-lab R&D, DNS-verified namespace).

Uptime history 43 hours of history · worst hour 0%
43 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
130 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add channel-lab --transport http https://studiolabsc.dedyn.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "channel-lab": {
      "url": "https://studiolabsc.dedyn.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.channel-lab]
url = "https://studiolabsc.dedyn.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "channel-lab": {
      "url": "https://studiolabsc.dedyn.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "channel-lab": {
      "url": "https://studiolabsc.dedyn.io/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://studiolabsc.dedyn.io/mcp streamable-http answering 130 ms 9 min ago

channel-lab — questions

Answers built from our own checks of this server.

Is channel-lab 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 130 ms. The bar chart above shows every period we have measured.
The registry lists channel-lab 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 channel-lab?
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 channel-lab need an API key?
No. channel-lab 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.