updated 2026-11-10 04:07 UTC

Browser Tools MCP

Repository Website

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 4.6 / 10
Provenance None
Signed commits 32%
Last push 13d ago
Advisories None known
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 68.5/100 (Grade B), ranked #414 of 1374 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 4.6/10; 32% of recent commits are signed; no published advisory affects its latest release (@agentdeskai/browser-tools-mcp); last pushed 2026-10-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Browser Tools MCP 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

Chain of custody

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

  1. Source Partly signed

    github.com/AgentDeskAI/browser-tools-mcp, MIT, last pushed 2026-10-28. 32% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review3
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 3
    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 9

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @agentdeskai/browser-tools-mcp 2.0.4. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-09 OSSF Scorecard: 3.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Browser Tools MCP’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 Browser Tools MCP compares in MCP Servers

  1. #241 Brave Search MCP Server 68.6 +0.1
  2. #242 Amazon Ads MCP 68.6 +0.1
  3. #243 Browser Tools MCP 68.5 this agent
  4. #244 Dav MCP 68.5 ±0
  5. #245 Terraform MCP Server 68.4 −0.1

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

Where the 68.5 comes from

HVTrust dimensions vs the MCP Servers average

68.5 / 100 · 100.0% confidence

Browser Tools MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.3 / 25
3.5 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.8 / 20
5.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
14.2 / 20
6.6 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-09
Rank Moved
Rank dropped 19 spots (#391 → #410)
2026-10-29
Rank Moved
Rank rose 63 spots (#441 → #378)
2026-10-27
Rank Moved
Rank rose 56 spots (#499 → #443)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/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.
Compare with another agent
View MCP Servers Report missing data
80.2
Activity sub-score · out of 100
#243
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 B 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-11-10 04:07 UTC · Repo last pushed 13 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
7.3k
Forks
538
Last Push
2026-10-28
13 days ago
Commits (4 wk)
47
Downloads (7d)
4,672
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▼4
was #410

Analysis

Activity Inputs

80.2 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
23.2 / 25
ActivityRecent commits
21.0 / 25
CommunityFork signal
12.7 / 20

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 4.6/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?
Maintained. Last push was 13 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?
32% 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

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 27Grade 5HVTrust 3Score 2Scorecard 1Delisted 1Listed 1MCP 1
2026-11-09
Rank Moved
Rank dropped 19 spots (#391 → #410)
2026-10-29
Rank Moved
Rank rose 63 spots (#441 → #378)
2026-10-27
Rank Moved
Rank rose 56 spots (#499 → #443)
2026-10-26
Grade Changed
Trust grade C → B
2026-10-26
Rank Moved
Rank rose 26 spots (#525 → #499)
2026-10-23
Grade Changed
Trust grade B → C
2026-10-18
Rank Moved
Rank dropped 20 spots (#479 → #499)
2026-10-16
Grade Changed
Trust grade C → B
2026-10-16
Rank Moved
Rank rose 348 spots (#824 → #476)
2026-10-16
HVTrust Changed
HVTrust up 10.5pts (55.6 → 66.1)
2026-10-16
Activity Score Changed
Activity score up 28pts (52 → 80)
2026-10-15
Rank Moved
Rank dropped 13 spots (#811 → #824)
2026-10-12
Rank Moved
Rank dropped 15 spots (#783 → #798)
2026-10-09
Rank Moved
Rank dropped 16 spots (#755 → #771)
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)
GitHub → Website → npm: @agentdeskai/browser-tools-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 68.5 Grade B
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.4 · Raw JSON