# @mehmoodqureshi/chrome-mcp Drive your real Chrome over MCP: real logins and cookies, multi-tab automation, deny-all by default. - **Type:** MCP server - **Trust:** 85/100 (A), scored on the package rubric - **Verification:** verified (build provenance) - **Version:** 0.9.12 - **Author:** io.github.Mehmoodqureshi - **License:** Unknown - **npm:** @mehmoodqureshi/chrome-mcp - **Source:** https://github.com/Mehmoodqureshi/chrome-mcp - **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport) ## Trust 85/100 (A), scored on the package rubric - Publisher verified: no - Build provenance: verified attestation - npm trusted publishing (OIDC): yes - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-09-24T09:57:00.660Z - **Version scanned:** 0.9.12 - **CVEs:** none found by OSV at scan time ## Tools 40 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `tabs_list` — List open browser tabs. - `tab_select` — Make a tab active by tabId. - `tab_new` — Open a NEW tab (optionally at a URL) and focus it. Prefer this over `navigate` when the user says "open"/"go to" a site — `navigate` REPLACES the current tab. P - `tab_close` — Close a tab by tabId. - `navigate` — Navigate a tab to a URL, REPLACING its current page. Acts on the active tab unless tabId is given — to open a site without losing the current page, use `tab_new - `back` — Go back in history. - `forward` — Go forward in history. - `reload` — Reload the active (or given) tab. - `click` — Click an element. Target by selector, a snapshot ref, or role+name (e.g. role:"button", name:"Sign in") - the locator needs no snapshot first. trusted=true uses - `type` — Type text into an element (target by selector, ref, or role+name). trusted=true sends real keystrokes (works on React/Vue controlled inputs). - `select_option` — Select option(s) of a (target by selector or ref) — uploads without the OS dialog. Requires --enable-uploads. `files` are absolute local paths. - `frames_list` — List the tab's frames (the top document plus every iframe the extension can reach), with each frame's id and URL. Use it when a selector that should match does - `console_logs` — Console output and uncaught errors recorded on the page (requires --enable-observers). This is how you find out WHY a page misbehaved rather than only what it l - `network_log` — Requests the page made - fetch and XMLHttpRequest with method, URL, status and duration (requires --enable-observers). Set includeResources:true to also list sc - `dialogs` — Native dialogs (alert/confirm/prompt/beforeunload) the page raised, and how they were answered (requires --enable-observers). With observers on, dialogs are int - `print_pdf` — Render the page to PDF through Chrome's own print pipeline and save it to the task's results/ dir. Returns the path and size, not the bytes - a PDF is not somet - `chrome_status` — Report backend/session status: paired browser profiles and how each was named, and flags for switched-off capabilities. - `auth_check` — Is the tab sitting on a sign-in wall? Reads the page (URL, title, password fields, sign-in controls) and returns { authRequired, confidence, signals }. Use it a - `profile_use` — Switch the active browser profile (identity). Subsequent downloads, results, screenshots, and the action log are stored under profiles//. Resets the activ - `profile_rename` — Rename an automatically named browser profile (e.g. "profile-2" -> "work"). The name sticks across restarts; its saved artifacts move with it. - `task_new` — Start a new task (run) under the active profile. Creates profiles//tasks// with downloads/, results/, screenshots/ and makes it the active task s - `tasks_list` — List every task across all profiles under the data dir, with sizes and download counts. - `task_status` — Report the active profile/task and the folder paths where this run's artifacts are stored. - `batch` — Run multiple tool calls in one request — parallel (default) or serial. Each op is { tool, args } and goes through the same policy gate, rate limit, and error ha ## Install **Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"chrome\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@mehmoodqureshi/chrome-mcp\"\n ]\n }\n }\n}" ``` ## Blast radius Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs commands; runs on your machine. - Floor 46, ceiling 74 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/%40mehmoodqureshi%2Fchrome-mcp - Install plan: https://forgeregistry.com/api/v1/packages/%40mehmoodqureshi%2Fchrome-mcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mehmoodqureshi%2Fchrome-mcp - HTML page: https://forgeregistry.com/registry/%40mehmoodqureshi%2Fchrome-mcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.