W
wd041216-bit/zero-api-key-web-search
Web search for agents, with no API key
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Install command from the repository
pip install zero-api-key-web-search
Parsed from the README we fetched on 2026-11-07; we have not executed it.
This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
pip install zero-api-key-web-search
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
pip install zero-api-key-web-search. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/wd041216-bit-zero-api-key-web-search/)
- Source
- awesome · https://github.com/wd041216-bit/zero-api-key-web-search
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.