Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

qsearch

by theYahiaversion 0.4.0i★ 4iRuns in the cloudOfficial site ↗
Registry nameio.github.theYahia/qsearch

How to install

What it does

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

  • Connects Runs in the cloud
  • Account or key No key needed
  • Category Search & AI memory

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6291 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6021 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2091 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity8/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score16/100

Quality: Passed 3/4 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/4 checks · Runs on your computer

We hid some of the commands

Connect by URL: the server address did not answer when we checked

No install path has passed yet. See the maker’s instructions or pick another server in this category · Maker’s install instructions · Others in this category

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect qsearch yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

ChatGPT cannot connect qsearch yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

What you can do instead

B · Others in Search & AI memory that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect qsearch yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

Cursor cannot connect qsearch yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

VS Code cannot connect qsearch yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

No install path has passed yet. See the maker’s instructions or pick another server in this category

Stuck? Ask people who use qsearch💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
Apache-2.0
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
0.4.0
Published to registryi
Apr 29, 2026
Code last changedi
Sep 3, 2026
Last checked
Nov 18, 2026
Maker
theYahia
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

The server did not answer when we last checked, so we could not read its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account theYahia, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 months ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • ✕ Fail

    Endpoint responds

    Did not respond within 6 seconds when we checked

  • – Not applicable

    Sign-in with OAuth

    Did not respond within 6 seconds when we checked

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

The cloud address answered 0 of the last 4 checks · no answer last time · checked Nov 18, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/theyahia-qsearch.svg)](https://mcp.popnx.com/en/servers/theyahia-qsearch)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Search & AI memoryi

  • More stars than 88% of the other 6394 servers in this category
  • Published to the registry more recently than 9% of the other 6394 servers in this category
  • Basic checks equal to or better than 51% of the other 6394 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is qsearch safe?

It passed 3 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 3 months ago, and the latest version (0.4.0) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

by every-appWidely used★ 28.2KUpdated 5 days ago

Runs in the cloud✓ everyapp.com

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsWidely used★ 5.2KUpdated 2 months ago

Runs in the cloud✓ service owner · exa.aiTried by the PopNx team

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

by MicrosoftDocsWidely used★ 2KUpdated 12 months ago

Runs in the cloud✓ service owner · microsoft.comTried by the PopNx team

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

by proxysoulGrowing★ 1.6KUpdated 2 months ago

Runs in the cloud✓ empryo.com
Compared with similar ones
This one
qsearch
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesYesYesNoNo
Basic checks3/45/52/44/44/44/4
LicenseApache-2.0MITMITCC-BY-4.0NOASSERTIONApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

qsearch

I built this for my own daily research. After running 100+ research sprints, my agent kept hallucinating because it read 200-char snippets. qsearch gives it full content with multi-engine provenance — running locally, owned by me.

AI agents lose 17–33% of facts to hallucination because they read 200-character snippets, not full pages (Stanford 2024). Existing search APIs hide *which engines agreed* on a result. Existing knowledge graphs are enterprise-priced or vendor-locked.

qsearch is the open-source search layer that gives agents full content with multi-engine provenance — running on your machine, owned by you, ready for MCP today.

✅ v0.4.0 live at [qsearch.pro](https://qsearch.pro). Multi-engine attribution, trust corpus with per-URL provenance (engines[], sweep_count, trust_score), corpus viewer at /ui, MCP-over-HTTP for Claude Code and any spec-compliant client.

📖 Architecture: ARCHITECTURE.md · Vision: docs/VISION.md · Technical spec: docs/TRUST_MESH.md · Federation deep-dive: docs/FEDERATION_ARCHITECTURE.md

Demo

60-second tour: /health (it's up, local) → /sweep (multi-engine engines[] attribution) → /verify (does the cited source actually support the claim?). Reproduce it locally with bash scripts/record-demo.sh after npm start — see docs/launch/README-demo-embed.md.

Quick start

Run it in 5 minutes — free tier, no API key:

git clone https://github.com/theYahia/qsearch.git && cd qsearch

cp .env.example .env.local # works as-is on the $0 SearXNG tier docker compose up -d # Meilisearch + Qdrant + SearXNG npm install && npm start # → qsearch on http://localhost:8080

multi-engine attribution in one call

curl -X POST http://localhost:8080/sweep \ -H "Content-Type: text/plain" \ --data-binary $'t1|self-hosted search engine\n'

→ parsed_snippets.md with "Engines: google, duckduckgo, brave (count=3)"

The broad sweep tier runs on self-hosted SearXNG and costs nothing. Add a Brave key only when you want the focused/critical tiers. Full setup (Brave key, Ollama, MCP server) below.

Full setup — Brave BYOK + local LLM + MCP server

# 1. Clone

git clone https://github.com/theYahia/qsearch.git cd qsearch

2. Get a Brave Search API key (BYOK, $5/mo for ~1000 queries)

→ https://brave.com/search/api/ → sign up → copy key

3. Configure

cp .env.example .env.local

Set BRAVE_API_KEY=your_key

Set SEARXNG_URL=http://localhost:8888 (for multi-engine attribution)

4. Start infrastructure (Meilisearch + Qdrant + SearXNG)

docker compose up -d

5. (Optional) Pull Ollama models for local LLM cleaning + embedding rerank

Without them, search still works — just no cleaned_markdown and no rerank.

ollama pull qwen2.5:7b-instruct # ~5GB, cleaner (used by /sweep_context) ollama pull nomic-embed-text # 274MB, embedding rerank (Phase B)

6. Install & run

npm install npm start # → qsearch v0.4.0 on http://localhost:8080

7. (Optional) MCP server for Claude Code / Workbench / OpenClaw

npm run start:mcp # → http://0.0.0.0:8081

8. Test multi-engine attribution

curl -X POST http://localhost:8080/sweep \ -H "Content-Type: text/plain" \ --data-binary $'t1|self-hosted search engine\n'

→ parsed_snippets.md with "Engines: google, duckduckgo, brave (count=3)"

BYOK design: Brave key + SearXNG + Ollama all stay on your machine. No data exfiltration.


How I use it daily

Every research sprint I run a dual sweep:

# Brave sweep (primary, authoritative)

python research/scripts/brave_sweep.py queries.txt _raw_data/topic_2026-04-28/brave/

qsearch sweep (secondary, auto-indexes into corpus)

curl -X POST http://localhost:8080/sweep?topic=my_topic \ -H "Content-Type: text/plain" --data-binary @queries.txt

After 10+ sprints on the same domain, /corpus/top?min_engines=3 shows which URLs survived multiple independent search engines across multiple sessions. Those are the ones I actually trust.


Why qsearch exists

Every AI agent today hits the same broken loop:

Agent → Tavily/Exa/Serper API → 200-char snippets → hallucinated answer

Three failures:

  1. Snippets aren't enough. Stanford's 2024 production RAG audit measured 17–33% hallucination on Lexis+ AI and Westlaw despite "hallucination-free" claims. On Wikipedia QA, full content beats snippet-RAG by +7.3pp (arxiv 2501.01880).
  1. No trust signal. Search APIs return ranked lists without telling you *which engines agreed*. SEO-spam at position 3 looks identical to authoritative source at position 4.
  1. No memory. Every search starts from zero. The same trash gets surfaced again. The same authority goes unrecognized.

qsearch addresses all three:

  • Full content fetched and cleaned, not just snippets.
  • `engines[]` field per result — Google + DDG + Brave + Qwant + Startpage attribution exposed (via SearXNG aggregation).
  • Local corpus accumulates — every URL grows a trust profile across sweeps.

How it works

flowchart LR

A[Your agent] -->|query| Q[qsearch] Q -->|fan out| B[Brave Search API] Q -->|fan out| S["SearXNG\n(Google, DDG, Brave, Qwant, …)"] B -->|results| Q S -->|results + engines[]| Q Q -->|index by URL| C["Local corpus\n(Meilisearch + Qdrant)"] C -->|trust score| Q Q -->|re-ranked + full content + provenance| A

style C fill:#fde68a,stroke:#d97706,color:#000 style Q fill:#93c5fd,stroke:#2563eb,color:#000 style S fill:#86efac,stroke:#16a34a,color:#000

The yellow node is your private corpus. URLs found by 5 engines + 3 sweeps + 4 topics get a trust score that emerges naturally — no human ranking, no centralized authority, no cloud round-trip.

How qsearch compares

TavilyExaSerperBrave APISearXNGqsearch
Open source core❌❌❌❌✅✅
Full content (not snippets)partialpartial❌❌❌✅
Multi-engine attribution❌❌❌❌partial✅ (engines[])
Persistent local corpus❌❌❌❌❌✅
Trust score per URL❌❌❌❌❌✅
Self-hostable❌❌❌❌✅✅
MCP-nativepartial✅❌✅❌✅
BYOK upstream❌❌❌N/A✅✅

API — v0.4.0

Search endpoints
EndpointDescriptionBackend
POST /searchWeb search + corpus first, trust-weighted re-rankBrave or SearXNG
POST /sweepBatch search with priority/domain routing (see below)SearXNG / Brave / Academic
POST /cached_sweepSame as /sweep, with SQLite memcache layerSearXNG / Brave / Academic
POST /academic_searchPeer-reviewed papers via arxiv + PubMed + Semantic ScholarAcademic (free, no auth)
POST /sweep_contextLocal LLM page extraction (analogue of Brave LLM Context)Ollama qwen2.5
POST /newsNews searchBrave (requires key)
POST /contextDeep page extractionBrave (requires key)
POST /verifyCitation honesty check — does the cited URL actually support a claim? Returns Supported/Partial/Unsupported/Fabricated/Error + verbatim excerptLLM-as-judge (local Ollama qwen2.5 or DeepSeek)
POST /indexCrawl URL or index local .md globCrawl4AI
GET /trust/:urlTrust score + provenance for any URL in corpus—
GET /corpus/topTop URLs ranked by trust (?limit=20&min_engines=3)—
GET /corpus/statsCorpus size + counts—
GET /economy_reportSprint cost breakdown by backend + savings vs all-Brave—
GET /uiCorpus browser — search, trust scores, provenance modal—
GET /healthService status—

/search accepts: query, n_results (1–20), freshness (pd/pw/pm/py), search_lang, country, corpus_first (default true), corpus_only (default false).

/sweep accepts text/plain body with one query per line in the format label|query|priority:

  • priority ∈ broad (default, SearXNG, $0) / focused (Brave, ~$0.005) / critical (Brave + LLM Context, ~$0.01)
  • domain ∈ general (default) / scholarly (arxiv+PubMed+S2, $0) / ru (SearXNG with language=ru-RU bias, $0)
# Examples

bench_a|qdrant production latency benchmarks|focused sch_a|crispr cas9 off target effects|broad|scholarly ru_a|tadviser сро рейтинг 2025|broad|ru crit_a|self-hosted vector DB choice 2026|critical gen|simple search|broad # 2-field still works — defaults broad/general

Auto-indexes results into Meilisearch with engines[] and engine_count filterable.

/academic_search accepts JSON: { query, n_results (1-20), sources?: ["arxiv","pubmed","semanticscholar"] }. Fans out to all three in parallel, dedupes by DOI/title, returns interleaved top-N.

Multi-engine attribution example
curl -X POST http://localhost:8080/sweep \

-H "Content-Type: text/plain" \ --data-binary $'t1|self-hosted search engine 2026\n'

Output excerpt (parsed_snippets.md):

**1. GitHub - searxng/searxng**
  • URL: https://github.com/searxng/searxng
  • Engines: google, duckduckgo, brave, qwant (count=4)

A privacy-respecting, hackable metasearch engine...

2. random-blog.io/seo-spam-2026

  • URL: https://random-blog.io/seo-spam-2026
  • Engines: google (count=1)

Best self-hosted search engines you must try...

URL #1 has engine_count=4 — found by 4 independent engines. URL #2 has engine_count=1 — found by only one. The trust signal is built into the data, not bolted on.

Filter by trust in Meilisearch
curl -H "Authorization: Bearer masterKey" \

"http://localhost:7700/indexes/qsearch_corpus/documents?filter=engine_count%20%3E%3D%203"

Returns only URLs found by 3+ engines — your high-trust subset.

MCP integration

The MCP server lives in this repo — there is no npm package for it. Run it from source:

git clone https://github.com/theYahia/qsearch.git && cd qsearch

npm install npm start # REST API on :8080 — must be running first npm run start:mcp # MCP server (Streamable HTTP) on :8081

Claude Code

Add to ~/.claude/settings.json:

{

"mcpServers": { "qsearch": { "type": "http", "url": "http://localhost:8081" } } }

Available tools:

  • mcp__qsearch__web_search — web search via Brave or SearXNG
  • mcp__qsearch__sweep — batch research sweep with multi-engine attribution
  • mcp__qsearch__academic_search — peer-reviewed papers via arxiv + PubMed + Semantic Scholar
  • mcp__qsearch__sweep_context — Phase 3 local LLM page extraction (free, Ollama)
  • mcp__qsearch__verify_citation — does the cited URL actually support the claim? (Supported/Partial/Unsupported/Fabricated)
  • mcp__qsearch__economy_report — cost breakdown vs all-Brave bas

Only the beginning is shown; read the rest in the repo