updated 2026-09-26 06:32 UTC

Browser Tools MCP

AgentDeskAI/browser-tools-mcp

Monitor browser logs directly from Cursor and other MCP compatible IDEs.

MCP Servers TypeScript Listed MIT

Is Browser Tools MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.5 / 10
Provenance None
Signed commits 27%
Last push 45d ago
Compare Browser Tools MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Browser Tools MCP scores 57.1/100 (Grade C), ranked #715 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.5/10; 27% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Browser Tools MCP compares in MCP Servers

  1. #393 Mondaycom MCP 57.2 +0.1
  2. #394 Xiaohongshu MCP 57.2 +0.1
  3. #395 Browser Tools MCP 57.1 this agent
  4. #396 Logic Pro MCP 57.0 −0.1
  5. #397 Pyxel MCP 56.9 −0.2

Bars show each HVTrust score; the tick marks Browser Tools MCP’s 57.1.

Where the 57.1 comes from

HVTrust dimensions vs the MCP Servers average

57.1 / 100 · 100.0% confidence

Browser Tools MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
4.6 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
0.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
9.0 / 20
3.1 below avg 12.1
AdoptionLog-scaled stars · package downloads
14.1 / 20
6.9 above avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 311 spots (#1019 → #708)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 45 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Browser Tools MCP View MCP Servers Report missing data
54.8
Activity sub-score · out of 100
#395
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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 45 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
7.3k
Forks
536
Last Push
2026-08-12
45 days ago
Commits (4 wk)
0
Downloads (7d)
3,862
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▼2
was #713

Analysis

Activity Inputs

54.8 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
18.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.5 / 10
OpenSSF Scorecard · scanned Sep 18, 2026
Signed Commits
27%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 3
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Common questions about Browser Tools MCP

Browser Tools MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Browser Tools MCP publish package provenance?
No published build provenance is currently detected for Browser Tools MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Browser Tools MCP have an OpenSSF Scorecard?
Browser Tools MCP has an OpenSSF Scorecard score of 3.5/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 Browser Tools MCP actively maintained?
Slowing down. Last push was 45 days ago — keep an eye on whether activity resumes.
What license does Browser Tools MCP use?
Browser Tools MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Browser Tools MCP's commits signed?
27% of the last 100 commits to Browser Tools MCP 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
Browser Tools MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
high confidence
Match
Published package metadata matches the tracked repo
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 Browser Tools MCP'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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain Browser Tools MCP?

For maintainers

HVTrust scores Browser Tools MCP 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 19Listed 2HVTrust 2Grade 2Surface 1Score 1Scorecard 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 311 spots (#1019 → #708)
2026-09-23
HVTrust Changed
HVTrust up 32.6pts (24.5 → 57.1)
2026-09-22
Newly Listed
First tracked at rank #1019
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 13 spots (#704 → #691)
2026-09-11
Rank Moved
Rank dropped 50 spots (#622 → #672)
2026-09-09
Scorecard Added
OSSF Scorecard: 3.5/10
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 534 spots (#1156 → #622)
2026-09-09
HVTrust Changed
HVTrust up 20.2pts (38.8 → 59.0)
2026-09-09
Activity Score Changed
Activity score down 11pts (71 → 61)
2026-09-08
Rank Moved
Rank dropped 16 spots (#1140 → #1156)
2026-09-07
Rank Moved
Rank dropped 20 spots (#1120 → #1140)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1105 → #1120)
2026-09-05
Rank Moved
Rank dropped 39 spots (#1066 → #1105)
2026-09-04
Rank Moved
Rank dropped 24 spots (#1042 → #1066)
2026-09-03
Rank Moved
Rank dropped 64 spots (#978 → #1042)
2026-09-02
Rank Moved
Rank dropped 49 spots (#929 → #978)
2026-09-01
Rank Moved
Rank dropped 37 spots (#892 → #929)
2026-08-31
Rank Moved
Rank dropped 31 spots (#861 → #892)
2026-08-30
Rank Moved
Rank dropped 37 spots (#824 → #861)
2026-08-29
Rank Moved
Rank dropped 46 spots (#778 → #824)
2026-08-28
Rank Moved
Rank dropped 28 spots (#750 → #778)
2026-08-27
Rank Moved
Rank dropped 24 spots (#726 → #750)
2026-08-26
Rank Moved
Rank dropped 96 spots (#630 → #726)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Rank Moved
Rank rose 18 spots (#625 → #607)
2026-08-10
Newly Listed
First tracked at rank #625
GitHub → npm: @agentdeskai/browser-tools-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/browser-tools-mcp.svg)](https://hvtracker.net/agents/browser-tools-mcp)
HTML:
<a href="https://hvtracker.net/agents/browser-tools-mcp"><img src="https://hvtracker.net/badge/browser-tools-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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