open-webSearch
Related Servers
Alternatives to open-webSearch
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables web searches across multiple engines (DuckDuckGo, Bing, Google, SerpAPI, Google CSE, Tavily) with no API key required for the free engines, plus automatic fallback, caching, and webpage content fetching.MIT
- AlicenseAqualityCmaintenanceEnables web search without API keys using DuckDuckGo and Bing search engines, and retrieves webpage content. Supports multiple search engines simultaneously with privacy protection and asynchronous processing.248 PyPI10MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive web searching and content extraction using multiple search engines (Bing, Brave, DuckDuckGo) without API keys. Provides tools for full web searches with content extraction, quick search summaries, and single webpage content retrieval.1,194MIT
- FlicenseNot gradedqualityAmaintenanceEnables multi-engine searches across Google, Bing, Yahoo, DuckDuckGo, YouTube, eBay, and other sources, with access to weather, stock, news, image, shopping, and scholarly data. Supports JSON or Markdown responses and optional interactive result UIs.-
- AlicenseNot gradedqualityAmaintenanceEnables free-first English and Chinese web search through zero-key engines plus optional paid providers, returning compact multi-source evidence with bounded token and request budgets. Each result exposes provenance, independent source counts, routing decisions, and visible provider failures so agents can verify claims rather than receive unexplained empty results.167 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables English and Chinese web search without API keys by aggregating zero-key and optional paid providers, with compact multi-source evidence, visible provider failures, and bounded request/evidence budgets. Supports quick discovery, stricter verification, Chinese-source search, and URL extraction.167 npmApache 2.0
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: four tools fetch content from specific platforms (CSDN, GitHub, Juejin, Linux.do), while the search tool performs a general web search across multiple engines. There is no overlap in functionality, making tool selection straightforward.
The naming is mostly consistent with a 'fetchX' pattern for four tools (fetchCsdnArticle, fetchGithubReadme, fetchJuejinArticle, fetchLinuxDoArticle), but the search tool deviates by using a simple verb without a noun. All tools use camelCase, so the convention is uniform, but the pattern is not fully applied across all tools.
With 5 tools, the count is well-scoped for the server's purpose of open web search and content fetching. Each tool serves a specific, useful function without redundancy, making the set efficient and manageable for agents.
The tool surface covers fetching content from specific platforms and general web search, but there are notable gaps. For example, there is no tool to fetch content from other common sources (e.g., news sites, blogs beyond the listed ones), and no advanced search capabilities like filtering or pagination, which could limit agent effectiveness in broader web tasks.