Skip to main content
Glama
Sign In
search-rotation

search-rotation

by robin-bially
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to search-rotation

No user-submitted related servers found.

    Related Servers

    • web-mcp

      Chang-Tong
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for multi-engine web search and web page fetching, supporting parallel search, content extraction, and optional LLM-powered search summarization and deep search.
      5
      MIT

    • serp-it

      luka-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that aggregates web search results from multiple engines and optionally renders pages to Markdown, providing a unified search interface.
      10 npm
      3
      ISC

    • OwnSearch

      devops-infinity
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables federated web search and page extraction through a self-hosted MCP/HTTP server that discovers, scores, and rotates across a fleet of public SearXNG instances, failing over to healthy ones and attributing each result to its source instance and engine. It also fetches public pages as Markdown, text, or HTML with optional headless-browser rendering, same-host crawling, PDF parsing, and redirect reporting.
      Apache 2.0
    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

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    The two retrieval tools are explicitly separated by the known-URL vs discover-links distinction, and each description cross-references the other. The three configuration tools (get_engine_status, update_engine_config, open_dashboard) are read/write/human-view respectively, and the descriptions state those boundaries outright. No pair of tools appears to do the same thing.

    Naming Consistency5/5

    All five names follow a strict snake_case verb_noun pattern (fetch_url, search_web, get_engine_status, open_dashboard, update_engine_config). The verb choices are also semantically consistent: get for reading state, update for mutating it, open for launching.

    Tool Count5/5

    Five tools is tightly scoped to the stated purpose: two data-plane operations and three configuration/administration operations. Nothing appears redundant or missing at the count level.

    Completeness4/5

    Search, fetch, config read, config write and credential/dashboard access cover the full lifecycle of a rotating-provider retrieval server. Minor gaps remain, such as no batch multi-URL fetch and no way to probe live provider health, but these are either explicitly out of scope or workable around.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources