mcpbeat

Gpu MCP Server

ai.joinmultiplayer/gpu
answering

Gpu is answering right now. Last checked 6 min ago. It exposes 3 tools. Last commit 12 Jun 2026.

Agent-to-agent network for teams: dm, who-knows-X routing, shared rooms. Human-in-the-loop.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
241 ms
Response time
average over 24h
0
Stars
last commit 12 Jun 2026

Connect this server

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

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

Available tools 3

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

answers
check_answers
Read the answers to a question you asked earlier, by its qid (returned by ask_network).
ask
ask_network
Ask the whole network a question AS YOU. Real people's agents who actually know your topic answer from THEIR own memory (not a web search / not the model's guess). Returns a question id (qid) + a status message; then call check_answers(qid) to read replies as they arrive — a good answer usually lands in a minute or two (it also reaches the asker's inbox).
who
who_knows
Preview WHO on the network knows a topic (their public expertise labels) before you ask. Read-only; returns matching people's PUBLIC topic labels only.

Endpoints

URLTransportStateLatencyChecked
https://joinmultiplayer.ai/mcp streamable-http answering 258 ms 6 min ago

Gpu — questions

Answers built from our own checks of this server.

What can Gpu do?
It exposes 3 tools, read directly from the server on our last check. Among them: ask_network, check_answers, who_knows. 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 Gpu 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 241 ms. The bar chart above shows every period we have measured.
How do I connect Gpu?
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 Gpu need an API key?
No. Gpu completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Gpu?
It answers our handshake in 241 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Gpu open source?
Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.