qsearch MCP Server

by theyahia Your server? Claim it

not responding

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

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

Uptime history 48 days of history · worst day 0%

48 days agonow

0.0%

Uptime 24h

0 of 92 checks

—

Tools

hidden behind auth

550 ms

Response time

average over 24h

Stars

last commit 3 Sep 2026

What the code does

We read the source, 1 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command src/crawl/crawl4ai.js:15

    const child = spawn(pythonCmd, [WORKER, '--url', url, '--depth', String(depth)], {

Page executes code built at runtime public/index.html:164

    results.innerHTML = ''
    loading.classList.remove('hidden')

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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

URL	Transport	State	Latency	Checked
https://qsearch.pro/mcp	streamable-http	answering	550 ms	2 min ago

Alternatives to qsearch

same job, measured the same way

Pindoc

by var-gg

Code-pinned team memory for AI coding agents — typed artifacts, MCP-native, self-host.

local only

Ghostfox

by autokeren

Self-hosted stealth browser for AI agents: Firefox engine + Rust MCP runtime

local only

Forkflux MCP

by forkflux

Self-hosted multi-agent collaboration and audit layer for AI-assisted engineering teams

143 installs/wk local only

SAME - Stateless Agent Memory Engine

by sgx-labs

Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.

48 installs/wk local only

Forge — Agent Reputation Protocol

by pm577

Portable reputation for AI agents. MCP-native identity, vouching, trust scores.

local only

fastCRW

by us

Scrape, crawl, map & search the web. Open-source, self-hostable Rust crawler & search for AI agents.

answering

Realmint

by realmint-io

Agent-native scoring, search and routing for tokenized real-world assets across multi-chain.

16 tools answering

Tinysearch

by marcellm01

Self-hosted web research for MCP agents.

local only

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 92 checks got a reply (0.0%), average response time 550 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.