Browser Bridge (mukeshblackhat) MCP Server

browser-bridge-mcp npm v0.2.0

Published by mukeshblackhat — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
F
57/100
Last scanned
Trust
F · 57/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
F Why this grade 100 − 43.4 = 57/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−15.4 Dynamic evaluation of a non-literal value MTC-SRC-010 injection
−15.4 Assembled command execution and dynamic evaluation in the same server MTC-SRC-011 injection
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection
−6.3 Package runs install-time scripts MTC-SUP-010 supply-chain

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 the deduction.

Findings 6

high Dynamic evaluation of a non-literal value (src/client.js)MTC-SRC-010

In the server's implementation (`src/client.js:532`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: eval(

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/client.js

high Assembled command execution and dynamic evaluation in the same serverMTC-SRC-011

The implementation builds shell commands out of runtime values AND evaluates runtime values as code. Each is a separate arbitrary-execution primitive; a server exposing both gives anything that reaches either one a direct path to running attacker-chosen code.

Fix: Remove the dynamic eval, and pass command arguments as an argv array instead of building a shell string. If both are genuinely required, constrain and validate every value that can reach them.

Location: server implementation

high Dynamic code execution in server code (src/client.js)MTC-SRC-001

In the server's implementation (`src/client.js:532`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: eval(

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/client.js

high Shell/command execution in server code (bin/cli.mjs)MTC-SRC-002

In the server's implementation (`bin/cli.mjs:15`): 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: child_process

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 bin/cli.mjs

medium Untrusted input concatenated into a command sink (bin/cli.mjs)MTC-SRC-009

In the server's implementation (`bin/cli.mjs:131`): 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: execSync(`open "${

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 bin/cli.mjs

medium Package runs install-time scripts (postinstall)MTC-SUP-010

"browser-bridge-mcp" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package browser-bridge-mcp

What this scan could not see

Versions

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.

VersionScoreFindingsEngineScanned
v0.2.0 latest F 57/100 6 1.5.0 2026-07-23

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.

MCP Trust Score: F · 57/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/browser-bridge-mcp/badge.svg)](https://mcptrustchecker.com/registry/browser-bridge-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/browser-bridge-mcp"><img src="https://mcptrustchecker.com/registry/browser-bridge-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/browser-bridge-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 browser-bridge-mcp --online

Use the free API → How scoring works

Other implementations of Browser Bridge 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Developer Tools