Skills/Glama/chrome-devtools-mcp

chrome-devtools-mcp@r1

VERIFIED· install only

Publisher claims: "Enables browser automation and inspection by connecting to an already-running Chrome/Chromium over the DevTools protocol, with page-scoped routing so multiple clients can control separate tabs concurrently." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher mouse9527 · publishing for 5 daysInstalls 0Last detonated 5d ago
$npx skills add chrome-devtools-mcp
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified 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 code
What we saw when it ran
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is chrome-devtools-mcp@r1 safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-15 and scored it 82/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsaudit.sh:18 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfind "$ROOTFS" -xdev \( -name '.git' -o -name '.env' -o -name '.netrc' -o -name '.git-credentials' \Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssmoke.sh:80 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileserr, txt, _ = call("new_page", {"url": "file:///etc/passwd", "background": True})Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Process kill commandsmoke.sh:16 · Process kill command — agent can terminate processes[ -n "$SITE_PID" ] && kill "$SITE_PID" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandsmoke.sh:15 · Process kill command — agent can terminate processes[ -n "$CHROME_PID" ] && kill "$CHROME_PID" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandsmoke.sh:86 · Process kill command — agent can terminate processeskill "$CHROME_PID"; wait "$CHROME_PID" 2>/dev/null || true; CHROME_PID=""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈40 tok
1 file · 15 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.