stealth-chrome-devtools-mcp@2.1.62
CAUTION· not startedPublisher claims: "Undetectable browser automation for AI agents via the Model Context Protocol — one shared backend built for 50+ concurrent Claude Code sessions." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso youtube.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 68/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: document.cookie access; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
"nothing to contradict" (right for a capture), and a kill must refuse both.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill a process GROUP, and the backend gets its own with ``start_new_session``.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# The kill goes FIRST and is synchronous. A cancellation delivered whileFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.#: ``document.cookie='sid=1'``. The VALUE runs to the end of the line or the nextFix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.#: How long a browser the kill ladder could not end is waited for before it is calledFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.**F-993: the frozen state is captured BEFORE the heal can kill it.** The first failedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return subprocess.run( # noqa: S603 PERMANENT(fixed argv, no shell, absolute exe)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.us, and reaping on it would kill the browser the winner has just adopted andFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# tool deliberately did not kill it (F-888).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell._STATE_DIR_ENV_FILE = Path.home() / ".stealth-mcp" / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.After a kill the profile is asked once more who holds it (a lingering child would),Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# #55/#56): under ``extra="forbid"`` an ordinary Next.js ``.env`` holdingFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.that project's own ``.env`` happened to hold and shipped this tool's errors toFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Guarded off a LIVE backend: reaping would kill that backend's own browsers.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# product those locals hold proxy credentials (`proxy_utils`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."--safebrowsing-disable-auto-update": "automation default",Fix: Pin versions and sources; vendor anything fetched at install time.``document.cookie=...`` and pasted tokens live (F-I). The digest stillFix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.completed = subprocess.run( # noqa: S603 RELEASE-FIX-D (F-770)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."""Wait up to *timeout* for *pid* to be gone (the close path's own kill isFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.no environment variable and writes no ``.env`` still gets a working server thatFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Thin front-end over `singleton.stop_backend()` — no matching/killFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.#: ``userinfo@`` (proxy credentials are written exactly like this), then theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.kill escalation and the ``default`` seed refresh) and relaunches the same directoryFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.``shared_session.holder_of`` for who holds the profile) and the kill isFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* The ``.env`` FILE is read from OUR state dir, never from the cwd (seeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"Could not kill the unattached delegated browser {pid}: {error}",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Best-effort kill of a delegated Chrome we could not attach to.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.f"Pid {pid} was recycled since we launched it; refusing to kill "Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# whatever project folder the user happened to open. A cwd-relative ``.env``Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"No identity stamp for delegated pid {pid}; refusing to kill it",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return subprocess.Popen( # noqa: S603 PERMANENT(our own argv, no shell)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.for ``.env``: a typed model with coercion, strict rejection of unknown keys, andFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.and every heal, failed spawn and kill ladder closes something. On a backend sharedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.this" — and on that path the kill has exactly one home, which is what F-910Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell._signal = os.killFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.So the kill is no longer the first thing that happens to a browser we asked toFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* it is a process of ours — kill it;Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.no browsers and the kill site terminated a sibling still holding its user'sFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.dead in every tab, a force kill that did not end the process for seconds) the cause isFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.F4); it used to be shipped before the kill site decided, so a refusalFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.shutdown in flight to wait for and no cookie commit a kill could truncate. AFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.runpy.run_path(str(EMBEDDED_DIR / "server.py"), run_name="__main__")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.f"Could not kill browser pid {pid} left by failed spawn "Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.profiles, and paying a 5s force-kill wait for each stubborn one. On 2026-09-02Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.a defect in the fix; it is the owner's ruling read literally. We do not kill whatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.``--user-data-dir`` and fenced on a start TIME: kill what is on this directoryFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."refusing to kill it",Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# selection, spawn nothing rather than kill it; the next start re-selects.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.directory instead; it is to carry the spared entries' pids over to the killFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.carrying ``--type`` therefore answers None — do not wait, kill as before —Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# What it is USED for is decided below, once the kill site answered.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# (`spawn_leak`, which calls `launch_reaped`; its kill rungs wait 3 + 2 s), andFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill whenever it can (it started two minutes earlier, and a dump is seconds).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.timing, is what makes it safe to kill a browser (F-808 —Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill path ran the instant the graceful close had been SENT, so it landed on aFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# verdict could kill a healthy backend: the winner used to release the lock atFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""A spawn whose caller was cancelled: kill the child and close its pipes."""Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for stealth-chrome-devtools-mcp@2.1.62 as of 4 h ago. This is the package itself, not its dependencies.
What would make this Verified
12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim devinosolutions: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- document.cookie access≈ +4 on the totalReplace encoded or assembled strings with plain literals and remove undeclared network calls.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.