mcpbeat Sign in

Mercury MCP Server

answering

Mercury is answering right now. Last checked 7 min ago.

Uptime history 48 days of history · worst day 93%
48 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
430 ms
Response time
average over 24h
API key
Access
streamable-http

Mercury does not always answer

Over the last week it answered 98.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

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

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.mercury.com/mcp streamable-http needs key 428 ms 7 min ago

Alternatives to Mercury

same job, measured the same way
Mem
by mem
answering
V
Melon
by melon
18 tools answering
Mermaid Chart
by mermaid-chart
25 tools answering
Mercury Number
by pipeworx-io

mercury-number MCP — wraps StupidAPIs (requires X-API-Key)

36 tools answering
Metaview
by metaview
answering

Mercury — questions

Answers built from our own checks of this server.

Why is there no tool list for Mercury?
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 Mercury working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 430 ms. The bar chart above shows every period we have measured.
How do I connect Mercury?
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: it refuses anonymous clients.
Does Mercury need an API key?
Yes. Every time we knock, Mercury 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 Mercury?
It answers our handshake in 430 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.