Skip to main content
Glama
yatotm

Tavily MCP Load Balancer

by yatotm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Tavily MCP Load Balancer

No user-submitted related servers found.

    Related Servers

    • tavily-mcp-proxy

      welyfun
      A
      license
      Not graded
      quality
      F
      maintenance
      A proxy MCP server for Tavily search and extract APIs with support for multiple API keys, random rotation, and bearer token authentication.
      MIT

    • tavily-proxy-mcp

      pzehrel
      A
      license
      A
      quality
      D
      maintenance
      A 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.
      5
      13 npm
      1
      MIT

    • mcp-nexus

      ykq007
      A
      license
      Not graded
      quality
      D
      maintenance
      A multi-provider MCP server that unifies Tavily and Brave Search APIs, with key management, admin UI, and flexible search strategies.
      10 npm
      22
      MIT

    • tavily-pool-mcp

      yanjin734-ltsm
      A
      license
      B
      quality
      D
      maintenance
      A local MCP server that exposes Tavily search as a tool and rotates across multiple API keys for reliability.
      1
      MIT

    • tavily-rotator-mcp

      dragonheartcra
      A
      license
      Not graded
      quality
      D
      maintenance
      Pools multiple Tavily API keys into a single local MCP server with round-robin rotation and automatic failover, exposing Tavily search, extract, crawl, map, and research tools to AI agents via stdio.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 5 tools

    Disambiguation2/5

    The tool set has significant overlap and ambiguity, particularly between 'search' and 'tavily-search', which appear to be identical based on their descriptions. Additionally, 'tavily-crawl', 'tavily-extract', and 'tavily-map' all involve web content processing, making it unclear when to use one over the others without more specific distinctions in their purposes.

    Naming Consistency3/5

    The naming is mixed: four tools use a consistent 'tavily-' prefix with descriptive suffixes (crawl, extract, map, search), but one tool is named simply 'search' without the prefix. This deviation breaks full consistency, though the overall pattern is still readable and not chaotic.

    Tool Count4/5

    With 5 tools, the count is reasonable for a web search and content analysis server, aligning well with typical scopes. It's slightly under the ideal range but not overly thin, as each tool (despite overlaps) covers different aspects of web interaction.

    Completeness3/5

    The server covers core web operations like search, crawling, extraction, and mapping, but there are notable gaps. For example, there's no tool for updating or managing saved searches, filtering results beyond basic parameters, or handling authentication for restricted content, which could limit agent workflows in more advanced scenarios.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources