ruyi-mcp
Related Servers
Alternatives to ruyi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for multi-engine browser automation with proxy rotation, enabling AI-driven web interaction and task execution across Camoufox, DrissionPage, and Browser Use.Apache 2.0
- AlicenseBqualityDmaintenanceBrowser automation MCP server using Camoufox anti-detect browser with fingerprint spoofing, geolocation/timezone spoofing, and human-like cursor movement.141Apache 2.0
- FlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server for browser automation with stealth patches, offering 50 tools for navigation, scraping, and session configuration. Runs via Docker and supports remote control from any MCP client.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for stealth browser automation that uses human-like interaction patterns to bypass bot detection via the Chrome DevTools Protocol. It enables users to navigate, interact with elements, and capture data from websites using undetectable behaviors like Bezier mouse movements and Gaussian typing delays.107 npm1MIT
- AlicenseBqualityBmaintenanceAnti-detection browser automation MCP server. 18 tools wrapping CamoFox REST API with stealth fingerprinting that passes bot detection.47201 npm113MIT
- AlicenseNot gradedqualityBmaintenanceA high-performance MCP server for browser automation via Chrome DevTools Protocol, enabling fast, low-cost, and anti-bot web interactions.23 npmMIT
TDQS
Scored across 59 tools
Multiple tools have overlapping purposes: ruyi_capture_start vs ruyi_intercept_requests vs ruyi_get_request_initiator all deal with network monitoring, and ruyi_human_move/click/drag overlap in behavior. Descriptions help but boundaries are fuzzy, causing likely misselection.
All tools share the 'ruyi_' prefix and mostly use snake_case, but the verb/noun order is inconsistent: ruyi_websocket_inject and ruyi_human_move are noun_verb while ruyi_emulate_geolocation and ruyi_get_cookies are verb_noun. Some names like ruyi_break_on_xhr mix prepositions, deviating from the predominant pattern.
59 tools is extremely high, far above the 50+ threshold even for a broad automation server. The count suggests significant redundancy (e.g., multiple capture/intercept and breakpoint tools) rather than a lean, well-scoped surface.
The tool set covers the major browser automation domains: navigation, DOM interaction, network capture/interception, breakpoints, human simulation, session export, and fingerprinting. Minor gaps exist (e.g., no direct window resize or full-page HTML retrieval, but these are workable via evaluate_script).