mcpbeat

qsearch MCP Server

io.github.theYahia/qsearch
not responding

qsearch is listed as active in the registry but did not answer our last check. Last commit 23 Jun 2026.

Multi-engine search for AI agents. Trust scoring, local corpus, MCP-native. Self-hostable, BYOK.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
19808 ms
Response time
average over 24h
2
Stars
last commit 23 Jun 2026

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 qsearch --transport http https://qsearch.pro/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "qsearch": {
      "url": "https://qsearch.pro/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.qsearch]
url = "https://qsearch.pro/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "qsearch": {
      "url": "https://qsearch.pro/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "qsearch": {
      "url": "https://qsearch.pro/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://qsearch.pro/mcp streamable-http answering 19808 ms 8 min ago

qsearch — questions

Answers built from our own checks of this server.

Is qsearch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 19808 ms. The bar chart above shows every period we have measured.
The registry lists qsearch 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 qsearch?
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 qsearch need an API key?
No. qsearch 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.
Is qsearch open source?
Yes — it is published under the Apache-2.0 licence, written in JavaScript, 2 stars on GitHub and 4 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.