W
wd041216-bit/zero-api-key-web-search
Web search for agents, with no API key
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项(本地服务器用 command + args,示例见 客户端接法) - 重启客户端
取自该仓库的安装命令
pip install zero-api-key-web-search
解析自我们于 2026-11-07 抓取的该仓库 README;我们未执行过。
这条是仓库自己写的安装方式,不是 MCP 客户端配置,所以不生成 JSON。
配置项的键名以你的客户端为准:客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
- 安装
pip install zero-api-key-web-search
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
pip install zero-api-key-web-search。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
我们收录于 2026-11-05;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
Zero-API-Key Web Search
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
⚡ Jev-Powered ⚡ — free neural search & evidence verification for AI agents.
Zero API keys. MCP-ready. Batch-filter, rerank and verify evidence locally at 100+ decisions/sec with an open Jev-class decision model.
## Why Zero-API-Key Web Search (Jev-Powered)
An agent that searches the raw web pays for everything it reads: context tokens, latency, and attention spread over SEO noise. Zero-API-Key Web Search puts a sieve between search and the agent:
1. Search the web with zero API keys (DuckDuckGo by default, self-hosted SearXNG for cross-validation, optional Bright Data for production SERP + Web Unlocker).
2. Sieve the results through Laya — an open-weight (Apache-2.0), non-autoregressive decision model that scores every result for relevance in a single forward pass (~35 ms on GPU, 100–330 questions/sec batched) with calibrated probabilities. It never generates text, so there is nothing to parse and nothing to hallucinate.
3. Verify claims with probabilistic stance classification (support / conflict / neutral per source) instead of pure keyword matching, then emit citation-ready evidence reports.
Every stage degrades gracefully: no Laya installed? The pipeline falls back to the lexical heuristic verifier and still works — Laya is an accelerant, not a dependency.
query ──► providers ──► cross-validate ──► ┌─────────┐ ──► LLM context pack
│ LAYA │ (citations only)
│ SIEVE │
noise ───────────────────►└─────────┘ ──► verify_claim
(dropped pre-context) (probabilistic stance)
## 30-Second Setup
bash
pip install zero-api-key-web-search # free search, no API key, no model download
zero-search "Python 3.13 release" --json
zero-verify "Python 3.13 is the latest stable release" --deep --json
zero-report "Python 3.13 stable release" --claim "Python 3.13 is the latest stable release" --json
## Add the Sieve (Optional, ~800 MB, Fully Local)
bash
pip install "zero-api-key-web-search[laya]" # pulls laya + torch
# Relevance-filter every search result before it reaches your agent
zero-search "react state management" --laya --laya-threshold 0.6 --json
# Probabilistic stance verification (laya-stance-v1 model)
zero-verify "Python 3.13 is the latest stable release" --laya --json
# Both, in the flagship evidence report
zero-report "gpt-5 release" --claim "GPT-5 is released" --laya --deep --json
On Apple Silicon it runs on MPS; on NVIDIA GPUs on CUDA; anywhere on CPU (slower but works).
Behind a network that can't reach Hugging Face? export HF_ENDPOINT=https://hf-mirror.com.
### What Laya does inside the pipeline
| Stage | Question asked (one forward pass per item) | Effect |
| --laya on search/context | "Is this result relevant and informative for the query?" | drops noise before it burns context tokens |
| --laya on verify/report | "Does this text support the claim?" + "Does it state or imply the claim is false?" | replaces regex conflict markers and keyword-overlap cutoffs with calibrated probabilities |
The verification blend becomes 0.55 × neural stance + 0.35 × source quality + 0.10 × freshness (vs. the lexical model's 0.45 × keyword overlap + …). The result payload keeps the full lexical sidecar so you can compare both classifiers on your own data.
Zero API keys. MCP-ready. Batch-filter, rerank and verify evidence locally at 100+ decisions/sec with an open Jev-class decision model.
## Why Zero-API-Key Web Search (Jev-Powered)
An agent that searches the raw web pays for everything it reads: context tokens, latency, and attention spread over SEO noise. Zero-API-Key Web Search puts a sieve between search and the agent:
1. Search the web with zero API keys (DuckDuckGo by default, self-hosted SearXNG for cross-validation, optional Bright Data for production SERP + Web Unlocker).
2. Sieve the results through Laya — an open-weight (Apache-2.0), non-autoregressive decision model that scores every result for relevance in a single forward pass (~35 ms on GPU, 100–330 questions/sec batched) with calibrated probabilities. It never generates text, so there is nothing to parse and nothing to hallucinate.
3. Verify claims with probabilistic stance classification (support / conflict / neutral per source) instead of pure keyword matching, then emit citation-ready evidence reports.
Every stage degrades gracefully: no Laya installed? The pipeline falls back to the lexical heuristic verifier and still works — Laya is an accelerant, not a dependency.
query ──► providers ──► cross-validate ──► ┌─────────┐ ──► LLM context pack
│ LAYA │ (citations only)
│ SIEVE │
noise ───────────────────►└─────────┘ ──► verify_claim
(dropped pre-context) (probabilistic stance)
## 30-Second Setup
bash
pip install zero-api-key-web-search # free search, no API key, no model download
zero-search "Python 3.13 release" --json
zero-verify "Python 3.13 is the latest stable release" --deep --json
zero-report "Python 3.13 stable release" --claim "Python 3.13 is the latest stable release" --json
## Add the Sieve (Optional, ~800 MB, Fully Local)
bash
pip install "zero-api-key-web-search[laya]" # pulls laya + torch
# Relevance-filter every search result before it reaches your agent
zero-search "react state management" --laya --laya-threshold 0.6 --json
# Probabilistic stance verification (laya-stance-v1 model)
zero-verify "Python 3.13 is the latest stable release" --laya --json
# Both, in the flagship evidence report
zero-report "gpt-5 release" --claim "GPT-5 is released" --laya --deep --json
On Apple Silicon it runs on MPS; on NVIDIA GPUs on CUDA; anywhere on CPU (slower but works).
Behind a network that can't reach Hugging Face? export HF_ENDPOINT=https://hf-mirror.com.
### What Laya does inside the pipeline
| Stage | Question asked (one forward pass per item) | Effect |
| --laya on search/context | "Is this result relevant and informative for the query?" | drops noise before it burns context tokens |
| --laya on verify/report | "Does this text support the claim?" + "Does it state or imply the claim is false?" | replaces regex conflict markers and keyword-overlap cutoffs with calibrated probabilities |
The verification blend becomes 0.55 × neural stance + 0.35 × source quality + 0.10 × freshness (vs. the lexical model's 0.45 × keyword overlap + …). The result payload keeps the full lexical sidecar so you can compare both classifiers on your own data.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/wd041216-bit-zero-api-key-web-search/)
- 来源
- awesome · https://github.com/wd041216-bit/zero-api-key-web-search
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。