Puppeteer Real Browser (eikaramba) MCP Server
@eikaramba/puppeteer-real-browser-mcp-server
npm
v1.5.29
Published by @eikaramba — 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.
MCP server for puppeteer-real-browser
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 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
2. Client adoption risk — 94 − 11 = 83. 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 |
|---|---|
| −10 | capability blast radius (critical) — 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.
Findings 5
high Shell/command execution in server code (dist/browser-manager.js)MTC-SRC-002
In the server's implementation (`dist/browser-manager.js:173`): 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: { execSync } = require('child_process'); const registryQueries = [ 'reg query "HKEY_CURRENT_USER\\So
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 dist/browser-manager.js
high Shell/command execution in server code (dist/index-original.js)MTC-SRC-002
In the server's implementation (`dist/index-original.js:422`): 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: { execSync } = require('child_process'); // Query Windows Registry for Chrome installation path const re
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 dist/index-original.js
high Shell/command execution in server code (dist/system-utils.js)MTC-SRC-002
In the server's implementation (`dist/system-utils.js:60`): 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: { execSync } = require('child_process'); const { timeout = 5000, encoding = 'utf8', stdio = 'pipe' } = options;
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 dist/system-utils.js
medium Untrusted input concatenated into a command sink (dist/system-utils.js)MTC-SRC-009
In the server's implementation (`dist/system-utils.js:63`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const result = execSync(`${command} ${args.join(' ')}`, { encoding, timeout,
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 dist/system-utils.js
low Shell/command execution in packaging/dev tooling (dist/browser-manager.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/browser-manager.test.js:17`): 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: i.mock('net'); vi.mock('child_process'); vi.mock('puppeteer-real-browser', () => ({ connect: vi.fn() })); describe('
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 dist/browser-manager.test.js
Tools 11
Each tool and what it can reach — statically extracted from the published source.
get_contentingests untrusted inputbrowser_closeno sensitive capabilitybrowser_initno sensitive capabilityclickno sensitive capabilityfind_selectorno sensitive capabilitynavigateno sensitive capabilityrandom_scrollno sensitive capabilityscreenshotno sensitive capabilitysolve_captchano sensitive capabilitytypeno sensitive capability
Show 1 more tool ↓
waitno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan 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.5.29 latest |
B 83/100 | 5 | 1.13.0 | 2026-09-07 |
Embed this score
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.
Verify this score yourself
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 @eikaramba/puppeteer-real-browser-mcp-server --onlineOther implementations of Puppeteer Real Browser 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Browser Automation
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