Ruishu MCP
Related Servers
Alternatives to Ruishu MCP
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceAn 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-- AlicenseBqualityBmaintenanceA 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.52223 npm3MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to browser DevTools via CDP, enabling real-time access to console logs, network requests, and page state.-
- AlicenseAqualityAmaintenanceAn MCP server that enables LLMs to drive a Chromium browser for web scraping, collecting structured data, and exporting to CSV.153 npmMIT

WebLoom Engineofficial
AlicenseNot gradedqualityCmaintenanceMCP 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.1MIT- AlicenseNot gradedqualityDmaintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.1MIT
TDQS
Scored across 3 tools
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.
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.
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.
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.