smart-web-search-mcp
Related Servers
Alternatives to smart-web-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceOne endpoint, five search providers. Search broker for AI agents with automatic fallback, RRF ranking, and budget enforcement. The LiteLLM of web search.1571 PyPI6MIT
- AlicenseAqualityFmaintenanceWeb search for AI agents across 6 engines (Serper, Brave, Exa, Tavily, Firecrawl, Perplexity) through one search tool. Routes each query to the cheapest engine that clears a quality bar and caches repeats. Hosted, streamable-HTTP, BYOK supported.11MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs and coding assistants to run web searches by concurrently aggregating multiple commercial search engines per scenario, merging and deduplicating URL-normalized results with per-call fallback. When no API keys or all commercial engines fail, it automatically degrades to key-free DuckDuckGo and Bing channels so search never goes offline.18 npmMIT
- AlicenseAqualityAmaintenanceEnables AI agents to perform reliable web searches through multiple vendors with automatic failover, keyless-first access, TTL caching, and concurrent request coalescing.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides multi-provider web search capabilities with fallback chains, semantic reranking, and content extraction for grounded agent retrieval.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to run English and Chinese web searches without an API key, combining zero-key engines with optional paid providers and returning compact, provenance-tagged evidence under request and token budgets. Provider failures stay visible instead of being silently dropped, and additional tools extract URLs, GitHub READMEs, and Chinese technical articles.118 npmApache 2.0
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its stated role as the default web search entry point is unambiguous.
A single snake_case name (smart_web_search) is clean and readable, and with only one tool there is nothing to be inconsistent with. No mixed conventions or vague verbs appear.
Web search is fundamentally a single operation, so one tool is a defensible scope rather than a mismatch. It is slightly thin in that provider targeting, filtering, or page fetching are not exposed as separate capabilities.
The search capability itself is unusually thorough, with multi-provider cascade routing, parallel/serial fallbacks, and both block and JSON output formats. The only notable gap is the absence of any companion operation such as fetching/extracting the content behind a result URL.