VRO Camoufox MCP
Related Servers
Alternatives to VRO Camoufox MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server for web automation that enables browser control, element interaction, content extraction, and monitoring using Playwright.76 npmISC
- AlicenseBqualityDmaintenanceA streamlined Model Context Protocol server that enables AI models to perform stealth browser automation using Patchright, avoiding detection by anti-bot systems while providing essential web interaction capabilities.423Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that connects to Chrome debugging ports, enabling browser automation with persistent login sessions.1025 npm10MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that combines Playwright browser automation with DevTools-style monitoring capabilities, enabling AI assistants to automate browser tasks and capture network/console logs.135 npmMIT
- FlicenseNot gradedqualityDmaintenanceA complete Model Context Protocol server that implements Selenium WebDriver for browser automation with advanced detection evasion capabilities, multi-browser support, and comprehensive web interaction functionalities.-
- FlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities for creating and testing Autoconsent rules, enabling LLMs to interact with web pages and test consent management platforms in a real browser environment.10-
TDQS
Scored across 12 tools
Each tool has a clear prefix-based purpose: artifact.* handles artifact lifecycle, browser.* manages the browser session, and listing.* deals with page extraction. Even the overlapping listing.enumerate_member_inventory and listing.crawl_member_inventory are distinguished by the latter being a higher-level traversal, with descriptions clarifying the relationship.
All tool names follow a consistent pattern of domain.snake_case_action, e.g., browser.start_session, listing.crawl_member_inventory, artifact.confirm_remote_sync. No mixed conventions or verb-style inconsistencies.
Twelve tools is within the ideal range and well-scoped across three subdomains: browser control (4), listing extraction (3), and artifact management (5). Each tool serves a distinct purpose and earns its place without redundancy.
The tool surface covers the core browser session lifecycle, listing inspection/traversal, and artifact management from creation through sync confirmation and cleanup. Minor gaps exist, such as no explicit artifact discovery for confirmed items or more granular browser interactions (e.g., navigation, clicking), but these are workable for the apparent scope.