chrome-local-mcp
npm
v1.3.0
Published by callmehuyv — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
A local Chrome browser automation MCP server powered by Puppeteer for Claude Code
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Tool "eval" appears to run shell commands or evaluate code (keyword "eval" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool eval
In the server's implementation (`browser-manager.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFile } = require('child_process'); // --- Configuration --- const CONFIG = { USER_DATA_DIR: path.join(os.homedi
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server browser-manager.js
Tool "eval" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool eval
"chrome-local-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: echo 'chrome-local-mcp installed. Add to Claude Code with: claude mcp add chrome_local node node_modules/chrome-local-mcp/mcp-server.js'
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package chrome-local-mcp
Each tool and what it can reach — statically extracted from the published source.
evalruns code / shellbatchno sensitive capabilityclickno sensitive capabilityclick_refno sensitive capabilityclose_browserno sensitive capabilityfill_formno sensitive capabilityget_inputsno sensitive capabilityget_linksno sensitive capabilityget_network_requestsno sensitive capabilityget_textno sensitive capabilitygo_backno sensitive capabilitylaunchno sensitive capabilitylist_pagesno sensitive capabilitynavigateno sensitive capabilitynetwork_monitorno sensitive capabilitynew_tabno sensitive capabilityocrno sensitive capabilitypress_keyno sensitive capabilityscreenshotno sensitive capabilityscrollno sensitive capabilityselectno sensitive capabilitysnapshotno sensitive capabilitytypeno sensitive capabilitytype_refno sensitive capabilitywait_forno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.3.0 latest |
A 92/100 | 4 | 1.13.0 | 2026-09-07 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan chrome-local-mcp --online
Model Context Protocol (MCP) server that integrates AgentQL data extraction capabilities.
Screenshot any URL or HTML as PNG/JPEG/WebP from your AI agent. Full-page, clean, no install.
MCP server for aria51 accessibility scanner
Bridge any browser web app to Claude Code via MCP
Browserbase’s official MCP server: cloud headless browsers for agents, with sessions and screenshots.
MCP server for AI web browser automation using Browserbase and Stagehand