原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

qsearch

作者:theYahia版本 0.4.0i★ 4i在云端运行官方网站 ↗
注册名称io.github.theYahia/qsearch

安装方法

What it does

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

  • Connects 在云端运行
  • Account or key No key needed
  • Category 搜索与 AI 记忆

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

timesfm

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

作者:google-research★ 35,6291 个 skill

Skill · 操作手册

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…

作者:BigBodyCobain★ 11,6021 个 skill

Skill · 操作手册

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

作者:gosom★ 8,2091 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度8/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分16/100

质量: 基础检查通过 3/4 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/4 项检查 · 在你的电脑上运行

我们隐藏了部分命令

通过地址连接:检查时服务器地址没有响应

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器 · 作者的安装说明 · 同类的其他服务器

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 qsearch

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

ChatGPT 暂时无法连接 qsearch

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

你可以改用这些方式

B · 搜索与 AI 记忆 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 qsearch

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

Cursor 暂时无法连接 qsearch

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

VS Code 暂时无法连接 qsearch

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

卡住了?问问正在用 qsearch 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
许可证i
Apache-2.0
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.4.0
发布到注册中心i
2026年4月29日
代码最后更新i
2026年9月3日
最近检查
2026年11月18日
作者
theYahia
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

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

全部应用及其优缺点 →

它能做什么

我们上次检查时服务器没有响应,所以无法读取它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 theYahia 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于3个月前

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • ✕ 未通过

    端点有响应

    我们检查时,6 秒内没有响应

  • – 不适用

    使用 OAuth 登录

    我们检查时,6 秒内没有响应

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

云端地址最近 4 次检查中有 0 次响应 · 最近一次没有响应 · 检查于 2026年11月18日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

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

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 6394 个服务器的 88%
  • 发布到注册中心的时间比此分类中其他 6394 个服务器的 9% 更新
  • 基础检查结果等于或优于此分类中其他 6394 个服务器的 51%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

qsearch 安全吗?

它在 4 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于3个月前,最新版本(0.4.0)于7个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

OpenSEO

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

作者:every-app广泛使用★ 2.8万5天前更新

在云端运行✓ everyapp.com

Exa

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

作者:exa-labs广泛使用★ 52422个月前更新

在云端运行✓ 服务方 · exa.aiPopNx 团队已实际试用

Microsoft Learn MCP

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

作者:MicrosoftDocs广泛使用★ 199712个月前更新

在云端运行✓ 服务方 · microsoft.comPopNx 团队已实际试用

Docs

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

作者:proxysoul正在增长★ 16262个月前更新

在云端运行✓ empryo.com
与相似项目对比
本项
qsearch
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是是是否否
基础检查3/45/52/44/44/44/4
许可证Apache-2.0MITMITCC-BY-4.0NOASSERTIONApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分;其余内容请在仓库中阅读