mcpbeat

Kaito Query Service MCP Server

io.github.TheSandemon/kaito-query
not responding

Kaito Query Service is listed as active in the registry but did not answer our last check.

AI LLM with Gemini, MiniMax, Replicate, OpenRouter. Vision, search, code review. USDC on Base.

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
0.0%
Uptime 24h
0 of 182 checks
—
Tools
hidden behind auth
215 ms
Response time
average over 24h
open, no key
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 5 min ago.

run in your terminal
claude mcp add kaito-query --transport http https://us-central1-sand-gallery-lab.cloudfunctions.net/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "kaito-query": {
      "url": "https://us-central1-sand-gallery-lab.cloudfunctions.net/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.kaito-query]
url = "https://us-central1-sand-gallery-lab.cloudfunctions.net/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "kaito-query": {
      "url": "https://us-central1-sand-gallery-lab.cloudfunctions.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "kaito-query": {
      "url": "https://us-central1-sand-gallery-lab.cloudfunctions.net/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://us-central1-sand-gallery-lab.cloudfunctions.net/mcp streamable-http answering 215 ms 5 min ago
https://us-central1-sand-gallery-lab.cloudfunctions.net/toolsCall streamable-http answering 220 ms 5 min ago

Kaito Query Service — questions

Answers built from our own checks of this server.

Is Kaito Query Service working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 182 checks got a reply (0.0%), average response time 215 ms. The bar chart above shows every period we have measured.
Is Kaito Query Service 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.
The registry lists Kaito Query Service as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Kaito Query Service?
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 Kaito Query Service need an API key?
No. Kaito Query Service completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.