A token-efficient MCP server for Chrome browser automation that uses direct CDP and accessibility-tree-based references for stable element selection across DOM changes.
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
When Vitest UI server is listening, arbitrary file can be read and executed
Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening
Zod denial of service vulnerability
process.env. You'll be asked to provide them before it can run.CHROME_PATH— Google Chrome, Chromium, or any Chromium-based browser (auto-detected on macOS/Linux/Windows; override with )PUBLIC_BROWSER_CORTEX_DIRPUBLIC_BROWSER_PROFILE— "Julian" npx public-browserPUBLIC_BROWSER_TELEMETRY— 1 / true — (disabled) Opt-in: upload anonymised Cortex patterns to the community endpointPUBLIC_BROWSER_TELEMETRY_ENDPOINT— URL https://cortex.public-browser.dev/v1/patterns Override the telemetry collection endpoint (must be HTTPS)ProgramFilesProgramFiles(x86)SILBERCUE_CHROME_DIFF_RETRY_MSSILBERCUE_CHROME_DIFF_SETTLE_MSSILBERCUE_CHROME_FULL_TOOLSSILBERCUE_CHROME_HEADLESS— true / false false Opt-in headless mode for CI/server environmentsSILBERCUE_CHROME_MINIMAL_TOOLSSILBERCUE_CHROME_PORT— 1–65535 9222 CDP debugging port. Non-default values spawn an isolated Chrome instance (separate --user-data-dir) that won't conflict with the user's browserSILBERCUE_CHROME_PROFILE— path — Chrome user profile directory (auto-launch only)SILBERCUE_PUBLISH_BRANCHSILBERCUE_PUBLISH_REMOTESILBERCUE_SCRIPT_PORT[](https://m8ven.ai/mcp/silbercue-public-browser-2q9weo)