Browserbeam MCP Server

@browserbeam/mcp-server npm v0.6.0

Published by @browserbeam — 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 Browserbeam — use browser automation as tools in Cursor, Claude Desktop, and any MCP client

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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 − 4 = 96. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — 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 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([browserbeam_upload]) co-exist with external-action tools ([browserbeam_upload]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [browserbeam_upload] → sinks [browserbeam_upload]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow browserbeam_upload → browserbeam_upload

Tools 19

Each tool and what it can reach — statically extracted from the published source.

  • browserbeam_uploadingests untrusted inputnetwork egress
  • browserbeam_checkno sensitive capability
  • browserbeam_clickno sensitive capability
  • browserbeam_closeno sensitive capability
  • browserbeam_create_sessionno sensitive capability
  • browserbeam_execute_jsno sensitive capability
  • browserbeam_extractno sensitive capability
  • browserbeam_fillno sensitive capability
  • browserbeam_get_sessionno sensitive capability
  • browserbeam_list_sessionsno sensitive capability
Show 9 more tools ↓
  • browserbeam_navigateno sensitive capability
  • browserbeam_observeno sensitive capability
  • browserbeam_pdfno sensitive capability
  • browserbeam_screenshotno sensitive capability
  • browserbeam_scrollno sensitive capability
  • browserbeam_scroll_collectno sensitive capability
  • browserbeam_selectno sensitive capability
  • browserbeam_typeno sensitive capability
  • browserbeam_waitno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.6.0 latest A 96/100 1 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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/browserbeam-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/browserbeam-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/browserbeam-mcp-server"><img src="https://mcptrustchecker.com/registry/browserbeam-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/browserbeam-mcp-server/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 @browserbeam/mcp-server --online

Use the free API → How scoring works

More in Browser Automation