deep-websearch
Related Servers
Alternatives to deep-websearch
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables federated multi-source research by fanning out queries across web, community, and social sources, deduplicating and interleaving results, and storing a persistent corpus for cross-checking.6MIT
- AlicenseNot gradedqualityAmaintenanceEnables English and Chinese web search starting from zero-key sources, returning compact multi-source evidence with provenance and visible provider failures. Requests and output stay bounded by configurable result, time, and evidence budgets, with paid providers used only when policy and credentials allow.118 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables English and Chinese web search through zero-key sources plus optional paid providers, returning compact multi-source evidence with visible provider failures and bounded request and evidence budgets.118 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables production-grade web research through MCP, combining local SearXNG search with hosted fallback providers, fetch and crawl tools, summarization, and budget guardrails.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run unified web searches across multiple providers such as Exa, Serper, Tavily, Firecrawl, and Jina, fusing results with reciprocal rank fusion, and to extract readable content from public web pages, PDFs, and video pages as Markdown. Provider chains are configurable, failures are isolated per provider, and responses report attempted, succeeded, failed, and skipped channels with source tracing and honest warnings.MIT
- AlicenseNot gradedqualityCmaintenanceEnables keyless web search, multi-backend URL fetching, and iterative multi-round research with provenance-tracked observations, all without API keys.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct operation: source_status is diagnostics, broad_search is search, and fetch_page/fetch_pages are single vs. batched retrieval. The fetch_page vs. fetch_pages pair could be momentarily confused, but descriptions clearly distinguish single-URL extraction from batch reading up to 10 pages.
All names use consistent snake_case (source_status, broad_search, fetch_page, fetch_pages), and the fetch_ prefix cleanly pairs the single/batch variants. source_status is noun_noun rather than the verb_noun pattern of the others, a minor deviation.
Four tools is a lean but sensible scope for a search-and-fetch server: one diagnostic, one search, and two retrieval tools. It is slightly thin (no dedicated source-listing or pagination tool), but each tool clearly earns its place.
The surface covers the core lifecycle: check source readiness, run broad search with citations, and extract evidence from single or multiple pages. Minor gaps exist (e.g., explicit source enumeration or result pagination), but agents can work around these via source_status and broad_search parameters.