Skip to main content
Glama
xuange520
by xuange520

Related Servers

Alternatives to Ruishu MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides browser-grade web access for AI agents, using Chrome's actual network stack to bypass anti-bot protections and return clean markdown.
      9
      -
    • A
      license
      B
      quality
      B
      maintenance
      A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.
      52
      223 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to browser DevTools via CDP, enabling real-time access to console logs, network requests, and page state.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server giving AI agents 86 tools for browser automation via Chrome DevTools Protocol, including navigation, click/fill ladders, network inspection, per-site cracks, and optional marketplace for site-specific knowledge packs.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role in the pipeline: initialization, data retrieval, and page interaction. There is no overlap in purpose or ambiguity about which tool to use.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: init_riushu_hook, get_intercepted_traffic, execute_page_action. This makes the set predictable and easy to navigate.

    Tool Count5/5

    With only three tools, the server is tightly scoped to a specific workflow. Each tool is necessary and contributes to a coherent pipeline without unnecessary bloat or missing essentials.

    Completeness5/5

    The tool set covers the full lifecycle of the interception workflow: setup, observation, and action. There are no obvious dead ends or missing operations required to accomplish the intended purpose.

    Maintenance

    ActivityNo data
    ResponsivenessSlow