search-rotation
Related Servers
Alternatives to search-rotation
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for multi-engine web search and web page fetching, supporting parallel search, content extraction, and optional LLM-powered search summarization and deep search.5MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for web search that does not die when an API key runs out.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that aggregates web search results from multiple engines and optionally renders pages to Markdown, providing a unified search interface.8 npm3ISC
- AlicenseAqualityBmaintenanceA self-hosted MCP server for web search with multi-engine support, combining search, URL fetching, and deep research along with proxy routing and deduplication.3MIT
- AlicenseNot gradedqualityBmaintenanceA lightweight MCP server providing web search via DuckDuckGo and page content extraction in multiple formats.1MIT
- AlicenseAqualityBmaintenanceEnables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.8MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: search_web for discovery, fetch_url for known-URL reading, get_engine_status for machine-readable config, open_dashboard for human-facing browser access, and update_engine_config for writing config. The descriptions explicitly disambiguate overlapping areas, such as directing read-config requests to get_engine_status instead of open_dashboard.
All five tools follow a consistent verb_noun snake_case pattern: search_web, fetch_url, get_engine_status, open_dashboard, update_engine_config. There are no deviations or mixed conventions.
Five tools is well-scoped for a search-rotation server: two core actions (search_web, fetch_url) plus three management/status tools (get_engine_status, open_dashboard, update_engine_config). No tool feels redundant or missing.
The surface covers the full lifecycle: discovery (search_web), content retrieval (fetch_url), status inspection (get_engine_status), configuration updates (update_engine_config), and human credential management (open_dashboard). No significant gaps for the stated domain of rotating web search and fetch providers.