mcpbeat

doing MCP Server

live.alpic.doing-v2-d5286fe8/doing
answering

doing is answering right now. Last checked 8 min ago. It exposes 2 tools.

simple task manager for your LLM

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
855 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 8 min ago.

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

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

doing
doing
Manage the doing task stack. Add a task, complete one, list tasks, or view the full stack with UI.
history
history
View all completed tasks in chronological order (from oldest to most recent)

Endpoints

URLTransportStateLatencyChecked
https://doing-v2-d5286fe8.alpic.live sse answering 264 ms 8 min ago

doing — questions

Answers built from our own checks of this server.

What can doing do?
It exposes 2 tools, read directly from the server on our last check. Among them: doing, history. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is doing 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 855 ms. The bar chart above shows every period we have measured.
How do I connect doing?
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 doing need an API key?
No. doing completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is doing?
It answers our handshake in 855 ms on average, which is faster than 8% 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.