mcpbeat

Studio Signal MCP Server

io.github.vfxprojoe/studio-signal
answering

Studio Signal is answering right now. Last checked 4 min ago. 71 installs a week from npm.

AI-powered media & entertainment intelligence — research, briefs, and market data.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 38 · avg 12 · -15% w/w
a month agotoday
Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
348 ms
Response time
average over 24h
71
Installs / week
npm and PyPI

Connect this server

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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://studiosignal.app/api/mcp streamable-http needs key 291 ms 4 min ago

Studio Signal — questions

Answers built from our own checks of this server.

Why is there no tool list for Studio Signal?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Studio Signal 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 348 ms. The bar chart above shows every period we have measured.
Is Studio Signal still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Studio Signal?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Studio Signal need an API key?
Yes. Every time we knock, Studio Signal answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Studio Signal?
It answers our handshake in 348 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Studio Signal?
The npm package @studiosignal/mcp-server was installed 71 times in the last week. Week over week that is -15%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.