
Siftdog
io.github.khsarvar由 GitHub 帳號 khsarvar 發布v0.3.0更新於 Oct 24, 2026
Self-hosted, Tavily-compatible web search, extract, crawl and map tools for AI agents.
概覽
自架、相容 Tavily 的 MCP 伺服器,讓助理能進行網頁搜尋、頁面擷取、網站爬取與網站地圖。
- 可以做什麼
- 透過 SearXNG 執行個體搜尋網頁,可選擇由檢索結果產生 AI 答案,並支援網域篩選(siftdog_search)。從最多 20 個指定網址擷取乾淨的 markdown 或純文字(siftdog_extract)。依深度、廣度、數量及路徑或網域篩選條件爬取網站(siftdog_crawl)。僅列出網站網址而不抓取內容(siftdog_map)。四個工具皆為唯讀。
- 適用情境
- 當你想為代理提供類似 Tavily 的搜尋、擷取與爬取能力,但偏好自行執行基礎設施、且不想使用搜尋 API 金鑰時適用。適合 Claude Desktop、Claude Code、Cursor 等本機用戶端,以及需要寬鬆授權自架方案的團隊。
- 執行需求
- 以 stdio 在本機執行,通常透過 uvx 啟動 siftdog 套件,或透過 HTTP 的 /mcp 連線至已執行的 Siftdog 伺服器。搜尋需要 SEARXNG_URL 指向已啟用 JSON 輸出的 SearXNG 執行個體;擷取、爬取與地圖不需它。若伺服器設定了 API_KEYS,用戶端需送出 Authorization Bearer 標頭。選用的 ANTHROPIC_API_KEY 用於啟用 include_answer。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Siftdog,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Siftdog — open-source, self-hosted Tavily alternative
[CI] [License: MIT] [PyPI] [Python 3.11+]
Website · Benchmark · Blog · Hosted waitlist
Siftdog is an open-source, self-hosted web search API for AI agents and LLM apps, and a drop-in
replacement for the Tavily API. It serves the same /search,
/extract, /crawl and /map endpoints with the same request and response shapes, so code
written for Tavily (including the official Python SDK and the LangChain integration) works
against your own server by changing only the base URL. It needs no search API key.
- Search through a SearXNG metasearch instance, with no search API keys
- Extraction of clean markdown or text from web pages with trafilatura
- Ranking: BM25 relevance blended with the upstream engine's order;
advanceddepth fetches each page and returns its most relevant chunks - Answers (
include_answer) written by Claude from the retrieved results - Crawling and site maps with depth, breadth, limit and regex path/domain filters
- MCP server for Claude Code, Claude Desktop, Cursor and other MCP clients, over HTTP at
/mcpor stdio withsiftdog mcp - SSRF protection: private and internal addresses are blocked, including via redirects and DNS rebinding
- MIT licensed
Use it as a drop-in Tavily replacement
Point the official Tavily clients at your Siftdog server with api_base_url. The key can be any
string when auth is disabled, or one of your API_KEYS.
LangChain, through langchain-tavily:
Tested with tavily-python 0.8.4 (search, extract, crawl, map; sync and async) and
langchain-tavily 0.2.18 (search, extract).
Quick start
Docker Compose (includes SearXNG)
The full stack, with a SearXNG instance for /search, using the published image:
Try a search:
If you set API_KEYS, add -H "Authorization: Bearer <key>". OpenAPI docs are served at
http://localhost:8000/docs.
Docker image only
/extract, /crawl and /map work on their own. For /search, point it at a SearXNG
instance with the JSON format enabled: -e SEARXNG_URL=http://your-searxng:8080. Images are
published for linux/amd64 and linux/arm64, tagged latest and by version (0.1.0, 0.1).
pip
Configuration is read from environment variables or a .env file (see
Configuration).
Use with MCP clients (Claude, Cursor, ...)
Siftdog is also an MCP server with four read-only tools:
siftdog_search, siftdog_extract, siftdog_crawl and siftdog_map.
Connect to a running Siftdog server (Streamable HTTP at /mcp). With Claude Code:
Or run it locally over stdio with uv, no server needed.
SEARXNG_URL is only needed for siftdog_search:
Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json) and most other clients
take the same command as JSON:
API keys work as for the REST API: send Authorization: Bearer <key>, or append
?api_key=<key> to the URL for clients that can't set headers (URLs can end up in logs, so
prefer the header). The HTTP endpoint only answers requests addressed to localhost unless you
list your hostname in MCP_ALLOWED_HOSTS.
Siftdog vs Tavily, Firecrawl and crw
Measured results: Siftdog vs Tavily search benchmark
(reproducible with bench/).
When to pick something else: if you'd rather not run infrastructure, or you want Tavily's neural reranking, use hosted Tavily. If you need JavaScript-rendered pages or a scraping platform with more features, look at Firecrawl or crw. Siftdog is for teams that want the Tavily API on their own servers under a permissive license.
FAQ
What is Siftdog?
Siftdog is an open-source web search and extraction API for AI agents. It reproduces the Tavily
API (/search, /extract, /crawl, /map) on infrastructure you run yourself, using SearXNG
for search results, trafilatura for content extraction and BM25 for relevance ranking.
Is Siftdog a drop-in replacement for Tavily?
For the four core endpoints, yes. The request and response fields match Tavily's, and the
official tavily-python SDK and langchain-tavily work by setting api_base_url. The
differences: relevance scores come from BM25 rather than a neural reranker, instructions
(crawl/map) and include_image_descriptions (search) are accepted but ignored, and Tavily's
/research endpoint isn't implemented.
Do I need a search API key?
No. Search results come from SearXNG, which queries public search engines. The only optional
key is ANTHROPIC_API_KEY, used when a request sets include_answer.
Does it work with LangChain?
Yes, through the official langchain-tavily package. Pass api_base_url pointing at your
Siftdog server, as in the example above.
Does Siftdog have an MCP server?
Yes. The API server exposes MCP over Streamable HTTP at /mcp, and uvx siftdog mcp runs it
over stdio for local clients such as Claude Desktop and Cursor. See
Use with MCP clients.
Why does /search return 502 "failing engines"?
SearXNG gets its results by querying public search engines (Brave, DuckDuckGo, Google and
others), and those engines rate-limit or CAPTCHA an IP that sends many searches. When every
engine is failing, Siftdog returns 502 with the engines and reasons, for example
failing engines: brave (Suspended: too many requests), duckduckgo (CAPTCHA), rather than an
empty result list your agent would mistake for "nothing found". Engines recover on their own,
from minutes to about a day. If some engines still work, you get their results and the server
logs which engines were down. To reduce blocking, enable more engines in
docker/searxng/settings.yml and avoid bursts of identical searches.
Is it safe to expose Siftdog on a public server?
Set API_KEYS so only your clients can call it. /extract and /crawl fetch caller-supplied
URLs, so Siftdog refuses private, loopback and link-local addresses, checked on every redirect and
at connect time against the exact address used, which also stops DNS rebinding.
Can I run it without Docker?
Yes: pip install siftdog, then run siftdog with SEARXNG_URL pointing at any SearXNG
instance with the JSON output format enabled. /extract, /crawl and /map work without
SearXNG.
Local development
API
All endpoints take JSON POST bodies and a Authorization: Bearer <key> header (a legacy
api_key body field is also accepted). If API_KEYS is empty, auth is disabled.
Differences from hosted Tavily: instructions (crawl/map) and include_image_descriptions are
accepted but ignored; relevance scores come from BM25, not a neural reranker.
Configuration
Environment variables (see .env.example): API_KEYS, SEARXNG_URL, ANSWER_ENABLED,
ANSWER_MODEL, ANSWER_EFFORT, FETCH_TIMEOUT, FETCH_CONCURRENCY, FETCH_MAX_BYTES,
ALLOW_PRIVATE_NETWORKS, CRAWL_MAX_LIMIT, MCP_ALLOWED_HOSTS.
MCP_ALLOWED_HOSTS lists the hostnames the /mcp endpoint answers besides localhost, for
example search.example.com,search.example.com:*. Requests addressed to any other host get
421, which protects a local server from DNS-rebinding attacks by web pages.
Security: /extract and /crawl make the server fetch caller-supplied URLs. Requests to
private, loopback and link-local addresses are blocked (including via redirects) unless
ALLOW_PRIVATE_NETWORKS=true. The check runs at connect time against the exact address being
connected to, so DNS rebinding can't get around it. Fetches of user URLs ignore
HTTP(S)_PROXY, since a proxy would hide the destination address. As defense in depth for
hostile multi-tenant deployments, also restrict egress at the network level.
License
Siftdog is released under the MIT License. The "Siftdog" name is covered separately by the trademark policy: use the code freely, but forks and hosted services need a different name.
來源:README.md,提交 3454d52
工具
0版本歷史
1- v0.3.0最新Sep 28, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分