Browser (ricardodeazambuja) MCP Server
@ricardodeazambuja/browser-mcp-server
npm
v1.4.0
Published by @ricardodeazambuja — 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.
Universal browser automation MCP server using Playwright. Works with Antigravity, Claude Desktop, and any MCP client.
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. 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.
Findings 10
high Shell/command execution in server code (src/utils.js)MTC-SRC-002
In the server's implementation (`src/utils.js:87`): 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 commonPaths = [ '/usr/bin/google-chrome', '/usr/bin/
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 src/utils.js
medium Dynamic module load from a non-literal (src/utils.js)MTC-SRC-005
In the server's implementation (`src/utils.js:53`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: playwright = require(source.path); playwrightPath = source.path; debugLog(`✅ Playwrig
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 src/utils.js
low Shell/command execution in packaging/dev tooling (tests/run-all.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/run-all.js:8`): 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: spawnSync } = require('child_process'); const fs = require('fs'); const path = require('path'); const testsDir = __dir
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 tests/run-all.js
low Shell/command execution in packaging/dev tooling (tests/test-browser-automation.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test-browser-automation.js:8`): 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: st { spawn } = require('child_process'); const readline = require('readline'); const fs = require('fs'); const path = 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 tests/test-browser-automation.js
low Shell/command execution in packaging/dev tooling (tests/test-mcp.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test-mcp.js:7`): 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: st { spawn } = require('child_process'); const readline = require('readline'); const path = require('path'); let reques
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 tests/test-mcp.js
low Shell/command execution in packaging/dev tooling (tests/test-media-tools.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test-media-tools.js:8`): 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: st { spawn } = require('child_process'); const path = require('path'); const readline = require('readline'); const serv
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 tests/test-media-tools.js
low Shell/command execution in packaging/dev tooling (tests/test-network.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test-network.js:8`): 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: st { spawn } = require('child_process'); const path = require('path'); const readline = require('readline'); const serv
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 tests/test-network.js
low Shell/command execution in packaging/dev tooling (tests/test-performance.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test-performance.js:8`): 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: st { spawn } = require('child_process'); const path = require('path'); const readline = require('readline'); const serv
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 tests/test-performance.js
low Shell/command execution in packaging/dev tooling (tests/test-security.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test-security.js:8`): 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: st { spawn } = require('child_process'); const path = require('path'); const readline = require('readline'); const serv
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 tests/test-security.js
low Shell/command execution in packaging/dev tooling (tests/test-storage.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test-storage.js:8`): 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: st { spawn } = require('child_process'); const path = require('path'); const readline = require('readline'); const serv
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 tests/test-storage.js
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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.4.0 latest |
A 93/100 | 10 | 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 @ricardodeazambuja/browser-mcp-server --onlineOther implementations of Browser 24
Independent packages implementing the same tool, scanned with the same engine. Compare all 25 side by side →
Playwright Tools for MCP
MCP server for AI agents to understand web page structure and content using Playwright
MCP server for browser automation.
MCP (Model Context Protocol) server that runs in the browser. Register tools and prompts on the page; expose them to a local MCP client (e.g. an agent) over WebSocket.
MCP server for browser console output capture
Security scan results for the Browser (npm) MCP server.
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