mcpbeat

Mission Control MCP Server

io.github.dinof777/mission-control
answering

Mission Control is answering right now. Last checked 11 min ago.

Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.

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

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
76.9%
Uptime 24h
70 of 91 checks
—
Tools
hidden behind auth
743 ms
Response time
average over 24h
API key or OAuth
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 11 min ago.

run in your terminal
claude mcp add mission-control --transport http https://mission-control-six-kohl.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mission-control": {
      "url": "https://mission-control-six-kohl.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mission-control]
url = "https://mission-control-six-kohl.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mission-control": {
      "url": "https://mission-control-six-kohl.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mission-control": {
      "url": "https://mission-control-six-kohl.vercel.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://mission-control-six-kohl.vercel.app/api/mcp streamable-http needs key 1052 ms 11 min ago

Mission Control — questions

Answers built from our own checks of this server.

Why is there no tool list for Mission Control?
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: 76.9% of checks in the last 24 hours got a reply.
Is Mission Control working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 70 of 91 checks got a reply (76.9%), average response time 743 ms. The bar chart above shows every period we have measured.
Is Mission Control 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 Mission Control?
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 Mission Control need an API key?
Yes. Every time we knock, Mission Control 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 Mission Control?
It answers our handshake in 743 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.