updated 2026-09-04 13:33 UTC

Browser Tools MCP

AgentDeskAI/browser-tools-mcp

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

MCP Servers TypeScript Grade D Listed MIT
39.5/100
Rank #1052 of 1320
Compare Browser Tools MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-12 · 23d ago
Recent change
Rank +7

Is Browser Tools MCP safe? Browser Tools MCP scores 39.5/100 (Grade D), ranked #1052 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 27% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#590 Unreal MCP Ue4 — 39.5 (D) → #591 Cursor History MCP — 39.5 (D) → #593 Openfate MCP — 39.4 (D) → #594 MCP Sqlite Tools — 39.4 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 10 spots (#1042 → #1052)
2026-09-03
Rank Moved
Rank dropped 64 spots (#978 → #1042)
2026-09-02
Rank Moved
Rank dropped 49 spots (#929 → #978)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
Compare with another agent Get email alerts for Browser Tools MCP View MCP Servers Report missing data
73.5
Activity sub-score · out of 100
#592
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-09-04 13:33 UTC · Repo last pushed 23 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
7.3k
Forks
529
Last Push
2026-08-12
23 days ago
Commits (4 wk)
17
Downloads (7d)
4,267
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▼10
was #1042

Analysis

HVTrust Dimensions vs MCP Servers

39.5 / 100 · 67.0% confidence

Browser Tools MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.4 / 25
8.1 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
15.5 / 20
3.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
14.1 / 20
7.9 above avg 6.2

Activity Inputs

73.5 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
21.8 / 25
ActivityRecent commits
15.7 / 25
CommunityFork signal
12.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
27%
of last 100 commits verified

Is Browser Tools MCP safe?

Public trust evidence for Browser Tools MCP 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 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?
No OpenSSF Scorecard data is currently published for Browser Tools MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Browser Tools MCP actively maintained?
Maintained. Last push was 23 days ago.
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-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 11Listed 1Surface 1
2026-09-04
Rank Moved
Rank dropped 10 spots (#1042 → #1052)
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 39.5 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON