Skills/npm/browser-mcp

browser-mcp@0.19.0

VERIFIED

Publisher claims: "mlola-mcp: a Model Context Protocol server that lets coding agents run browser tasks and get back what each run proves." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher mlola · publishing for 24 daysInstalls 4,097Last detonated 13 min ago
$claude mcp add browser-mcp -- npx -y @mlola/browser-mcp
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

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
what the tools do when called with real credentials

Reasonable to connect. No credential asked for, no third-party host named, Server started and answered tools/list.

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

What changed since 0.18.0

vet-skills diff browser-mcp 0.18.0 0.19.0

In the sandbox, this version reached for nothing 0.18.0 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-21 and scored it 91/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 25 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.8sprocessdependency install exit 0
25sclaimed5 tools: browser_run, browser_verify, browser_prove, browser_get_run, browser_list_runs
25stools06e93bd79f0626a2
25stools97ecd0d128b3651e
25stoolsa962a04c654ff8e8
25stools96ecbeb4872ac661
25stoolsd56afdde33443fc6
25sprocessscript backend runs setup only
25sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagedist/bin.d.ts:5 · npx invocation of non-well-known package — may execute untrusted code* claude mcp add mlola-browser -e TYPESAFE_API_KEY=… -- npx -y @mlola/browser-mcpFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/bin.js:5 · npx invocation of non-well-known package — may execute untrusted code* claude mcp add mlola-browser -e TYPESAFE_API_KEY=… -- npx -y @mlola/browser-mcpFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈67 tok
1 file · 20 in bundle
Tool list per prompt
≈2,854 tok
5 tools · 571 per tool
Handshake
951 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 522

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

Not checked against OSV yet; the weekly check has not reached this version.