tavily-rotator-mcp
Related Servers
Alternatives to tavily-rotator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a local stdio MCP proxy that distributes Tavily tool calls across multiple API keys, automatically handling rate limits and invalid keys to enable uninterrupted search, extract, crawl, map, and research operations.1MIT
- AlicenseNot gradedqualityCmaintenanceExposes pooled Tavily API keys through an MCP streamable HTTP endpoint, providing search, extract, crawl, map, research, and pool status tools with automatic key rotation and quota management.MIT
- AlicenseBqualityDmaintenanceA local MCP server that exposes Tavily search as a tool and rotates across multiple API keys for reliability.1MIT
- AlicenseAqualityDmaintenanceA proxy MCP server that connects to Tavily's official Streamable HTTP MCP, managing multiple API keys and automatically switching to the next one when the current key's quota is exhausted.523 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Tavily search and web data tools, enabling search, extract, crawl, and map operations through a simple HTTP or stdio interface.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server exposing 8 Tavily tools (web search, fetch, crawl, map, QnA, context, and deep research) via Streamable HTTP for AI assistants to perform live web retrieval and research.1-
TDQS
Scored across 6 tools
Each tool serves a clear, distinct function: search for queries, extract for single URLs, crawl for site-wide content, map for URL discovery, research for multi-source synthesis, and pool_status for internal health. There is minimal overlap, and the descriptions clarify when to use each.
All tools follow a consistent 'tavily_' prefix with lowercase snake_case verb/noun names. The naming pattern is predictable and clearly indicates the action (search, extract, crawl, map, research, pool_status), with no mixed conventions.
With 6 tools, the server is well-scoped for a web research domain. Each tool adds distinct functionality, and the count is comfortably within the ideal range, neither sparse nor bloated.
The toolset covers the core web research lifecycle: search, extract, crawl, map, and comprehensive research. Minor gaps exist, such as advanced search parameters or bulk operations, but these are not essential for typical workflows. The inclusion of a pool status tool shows attention to operational needs.