Browserbase MCP Server

Allow LLMs to control a browser with Browserbase and Stagehand

MCP Servers TypeScript Grade C Needs review Apache-2.0
50.7/100
Rank #448 of 1283
Compare Browserbase MCP Server

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Needs review
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-20 · 22d ago
Recent change
Warning +3

Is Browserbase MCP Server safe? Browserbase MCP Server scores 50.7/100 (Grade C), ranked #448 of 1283 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 →

Active listing, but review is needed
  • [5.1] repository is archived

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
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.
Review Flags
[5.1] repository is archived
59.0
Activity sub-score · out of 100
#152

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-08-11 21:02 UTC · Repo last pushed 22 days ago

Activity & Reach

Stars
3.4k
Forks
367
Last Push
2026-07-20
22 days ago
Commits (4 wk)
1
Downloads (7d)
HN mentions (30d)
Open Issues
34
Rank Change
▼4
was #444

Analysis

HVTrust Dimensions vs MCP Servers

50.7 / 100 · 100.0% confidence

Browserbase MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.7 / 25
2.7 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
3.0 above avg 8.8
Maintenance60% last-push freshness · 40% commit activity
11.7 / 20
0.8 below avg 12.5
AdoptionLog-scaled stars · package downloads
8.5 / 20
2.7 above avg 5.8

Activity Inputs

59.0 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
21.9 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
11.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.9 / 10
OpenSSF Scorecard · scanned Aug 10, 2026
Signed Commits
57%
of last 100 commits verified
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

Is Browserbase MCP Server safe?

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?
Maintained. Last push was 22 days ago.
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
medium confidence
Declared
Declared plugin/integration 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-07-13
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-07-13
Provider Added
Runtime surface grew — new detected provider dependencies: Browserbase, Google Gemini
2026-07-13
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-07-13
Activity Resumed
Activity resumed

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.

Reputation Timeline

Signal history
Rank 6Score 2Warning Issued 2Listed 1HVTrust 1Grade 1Fresh 1MCP 1Surface 1Surface 1Warning Cleared 1
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)
2026-07-13
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-07-13
Provider Added
Runtime surface grew — new detected provider dependencies: Browserbase, Google Gemini
2026-07-13
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-07-13
Activity Resumed
Activity resumed
2026-07-13
Grade Changed
Trust grade D → C
2026-07-13
Rank Moved
Rank rose 78 spots (#338 → #260)
2026-07-13
HVTrust Changed
HVTrust up 41.6pts (9.0 → 50.6)
2026-07-13
Activity Score Changed
Activity score up 57pts (0 → 57)
2026-07-12
Newly Listed
First tracked at rank #338

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.7 Grade C
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.3 · Raw JSON