updated 2026-10-11 12:08 UTC

Browserbase MCP Server

Repository Website by browserbase

Allow LLMs to control a browser with Browserbase and Stagehand

MCP Servers TypeScript Needs review Apache-2.0

Is Browserbase MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.9 / 10
Provenance None
Signed commits 57%
Last push 83d ago
Compare Browserbase MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Browserbase MCP Server scores 45.8/100 (Grade D), ranked #1085 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.9/10; 57% of recent commits are signed; last pushed 2026-07-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Browserbase MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships Browserbase MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/browserbase/mcp-server-browserbase, Apache-2.0, last pushed 2026-07-20. 57% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. Browserbase MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Browserbase MCP Server.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Browserbase MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Browserbase MCP Server compares in MCP Servers

  1. #629 Fattureincloud MCP 46.0 +0.2
  2. #630 KDAN PDF 45.9 +0.1
  3. #631 Browserbase MCP Server 45.8 this agent
  4. #632 Scrapegraph MCP 45.8 ±0
  5. #633 Pty MCP 45.7 −0.1

Bars show each HVTrust score; the tick marks Browserbase MCP Server’s 45.8.

Where the 45.8 comes from

HVTrust dimensions vs the MCP Servers average

45.8 / 100 · 100.0% confidence

Browserbase MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.7 / 25
2.7 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
6.5 / 20
5.7 below avg 12.2
AdoptionLog-scaled stars · package downloads
8.5 / 20
1.1 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 13 spots (#1063 → #1076)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signals The repo was last pushed 83 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[5.1] repository is archived
Compare with another agent Get email alerts for Browserbase MCP Server View MCP Servers Report missing data
46.8
Activity sub-score · out of 100
#631
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 12:08 UTC · Repo last pushed 83 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
3.4k
Forks
373
Last Push
2026-07-20
83 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
34
Rank Change
▼3
was #1082

Analysis

Activity Inputs

46.8 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
13.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.0 / 20

Common questions about Browserbase MCP Server

Public trust evidence for Browserbase MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Browserbase MCP Server publish package provenance?
No published build provenance is currently detected for Browserbase MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Browserbase MCP Server have an OpenSSF Scorecard?
Browserbase MCP Server has an OpenSSF Scorecard score of 3.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Browserbase MCP Server actively maintained?
Slowing down. Last push was 83 days ago — keep an eye on whether activity resumes.
What license does Browserbase MCP Server use?
Browserbase MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Browserbase MCP Server's commits signed?
56% of the last 100 commits to Browserbase MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Browserbase MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Browserbase MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Browserbase MCP Server?

For maintainers

HVTrust scores Browserbase MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 32Warning Issued 5Warning Cleared 4Score 1Surface 1Grade 1
2026-10-09
Rank Moved
Rank dropped 13 spots (#1063 → #1076)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-29
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-28
Warning Issued
Warning: eligibility issues detected
2026-09-25
Rank Moved
Rank dropped 11 spots (#1013 → #1024)
2026-09-23
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-23
Rank Moved
Rank dropped 613 spots (#401 → #1014)
2026-09-22
Rank Moved
Rank dropped 61 spots (#340 → #401)
2026-09-21
Rank Moved
Rank rose 671 spots (#1011 → #340)
2026-09-12
Rank Moved
Rank dropped 11 spots (#982 → #993)
2026-09-09
Rank Moved
Rank dropped 13 spots (#960 → #973)
2026-09-08
Rank Moved
Rank dropped 13 spots (#947 → #960)
2026-09-07
Rank Moved
Rank dropped 44 spots (#903 → #947)
2026-09-06
Rank Moved
Rank dropped 14 spots (#889 → #903)
2026-09-05
Rank Moved
Rank dropped 50 spots (#839 → #889)
2026-09-04
Rank Moved
Rank dropped 41 spots (#798 → #839)
2026-09-03
Rank Moved
Rank dropped 48 spots (#750 → #798)
2026-09-02
Rank Moved
Rank dropped 32 spots (#718 → #750)
2026-09-01
Rank Moved
Rank dropped 35 spots (#683 → #718)
2026-08-31
Rank Moved
Rank dropped 38 spots (#645 → #683)
2026-08-30
Rank Moved
Rank dropped 16 spots (#629 → #645)
2026-08-29
Rank Moved
Rank dropped 42 spots (#587 → #629)
2026-08-28
Rank Moved
Rank dropped 19 spots (#568 → #587)
2026-08-27
Rank Moved
Rank dropped 13 spots (#555 → #568)
2026-08-26
Rank Moved
Rank dropped 85 spots (#470 → #555)
2026-08-24
Rank Moved
Rank dropped 14 spots (#456 → #470)
2026-08-22
Rank Moved
Rank rose 13 spots (#470 → #457)
2026-08-19
Grade Changed
Trust grade C → D
2026-08-19
Rank Moved
Rank dropped 22 spots (#448 → #470)
2026-08-17
Rank Moved
Rank rose 11 spots (#458 → #447)
2026-08-13
Rank Moved
Rank dropped 14 spots (#432 → #446)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Rank Moved
Rank rose 16 spots (#448 → #432)
2026-08-10
Warning Issued
Warning: eligibility issues detected
2026-08-10
Rank Moved
Rank dropped 15 spots (#429 → #444)
2026-08-09
Warning Cleared
Warning cleared: eligibility issues resolved
2026-08-08
Rank Moved
Rank dropped 107 spots (#316 → #423)
2026-07-20
Warning Issued
Warning: eligibility issues detected
2026-07-20
Rank Moved
Rank rose 10 spots (#298 → #288)
2026-07-20
Activity Score Changed
Activity score up 6pts (56 → 62)
2026-07-15
Rank Moved
Rank dropped 22 spots (#274 → #296)
2026-07-14
Rank Moved
Rank dropped 14 spots (#260 → #274)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 45.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/browserbase-mcp-server.svg)](https://hvtracker.net/agents/browserbase-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/browserbase-mcp-server"><img src="https://hvtracker.net/badge/browserbase-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON