updated 2026-11-10 04:07 UTC

CloakBrowser MCP

Repository Website

⚡ CloakBrowser MCP server for AI agents: Playwright-powered browsing, clean tool forwarding, Docker support, and multi-session HTTP transport.

MCP Servers TypeScript Listed MIT

Is CloakBrowser MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.5 / 10
Provenance Attested
Signed commits 16%
Last push 5d ago
Advisories None known
Compare CloakBrowser MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: CloakBrowser MCP scores 83.7/100 (Grade A), ranked #122 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.5/10; 16% of recent commits are signed; no published advisory affects its latest release (cloakbrowser-mcp); last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How CloakBrowser 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 CloakBrowser 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/swimmwatch/cloakbrowser-mcp, MIT, last pushed 2026-11-05. 16% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Strong

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

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

  3. Published packages Linked and attested

    • npm cloakbrowser-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: cloakbrowser-mcp 1.15.1. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected

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 CloakBrowser 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 CloakBrowser MCP compares in MCP Servers

  1. #48 CrowdStrike Falcon MCP Server 84.0 +0.3
  2. #49 Scrivener MCP 83.9 +0.2
  3. #50 CloakBrowser MCP 83.7 this agent
  4. #51 Linux MCP Server 83.6 −0.1
  5. #52 Discord MCP 83.5 −0.2

Bars show each HVTrust score; the tick marks CloakBrowser MCP’s 83.7.

Where the 83.7 comes from

HVTrust dimensions vs the MCP Servers average

83.7 / 100 · 100.0% confidence

CloakBrowser MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.7 / 25
6.9 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.9 / 17
2.6 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.7 / 20
6.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.3 / 20
1.7 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-20
Rank Moved
Rank rose 16 spots (#104 → #88)
2026-10-19
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-10-19
Rank Moved
Rank dropped 25 spots (#79 → #104)
Maintainer Checklist
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
66.1
Activity sub-score · out of 100
#50
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 A 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 5 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
178
Forks
21
Last Push
2026-11-05
5 days ago
Commits (4 wk)
57
Downloads (7d)
784
npm
HN mentions (30d)
—
Open Issues
8
Rank Change
▲1
was #123

Analysis

Activity Inputs

66.1 / 100
StarsRepository reach
13.5 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
22.0 / 25
CommunityFork signal
6.2 / 20

Common questions about CloakBrowser MCP

Public supply-chain signals for CloakBrowser MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but CloakBrowser MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does CloakBrowser MCP publish package provenance?
Yes. CloakBrowser MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does CloakBrowser MCP have an OpenSSF Scorecard?
CloakBrowser MCP has an OpenSSF Scorecard score of 7.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 CloakBrowser MCP actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does CloakBrowser MCP use?
CloakBrowser MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are CloakBrowser MCP's commits signed?
16% of the last 100 commits to CloakBrowser 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
CloakBrowser 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
high confidence
Extensions
Extension based plugin/integration surface detected.
  • browser
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 CloakBrowser 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-10-19
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain CloakBrowser MCP?

For maintainers

HVTrust scores CloakBrowser 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 13Grade 3Score 2Delisted 1Listed 1HVTrust 1Provenance 1MCP 1Surface 1
2026-10-20
Rank Moved
Rank rose 16 spots (#104 → #88)
2026-10-19
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-10-19
Rank Moved
Rank dropped 25 spots (#79 → #104)
2026-10-18
Rank Moved
Rank rose 15 spots (#94 → #79)
2026-10-18
Activity Score Changed
Activity score up 6pts (63 → 69)
2026-10-04
Rank Moved
Rank rose 18 spots (#92 → #74)
2026-10-03
Rank Moved
Rank dropped 28 spots (#64 → #92)
2026-09-27
Rank Moved
Rank rose 22 spots (#87 → #65)
2026-09-25
Rank Moved
Rank rose 21 spots (#101 → #80)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 545 spots (#645 → #100)
2026-09-23
HVTrust Changed
HVTrust up 51.3pts (32.3 → 83.6)
2026-09-22
Newly Listed
First tracked at rank #645
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank dropped 10 spots (#97 → #107)
2026-09-14
Rank Moved
Rank rose 15 spots (#105 → #90)
2026-09-13
Rank Moved
Rank rose 10 spots (#115 → #105)
2026-09-05
Grade Changed
Trust grade B → A
2026-09-04
Activity Score Changed
Activity score up 5pts (48 → 53)
2026-09-03
Grade Changed
Trust grade A → B
2026-09-03
Rank Moved
Rank dropped 24 spots (#84 → #108)
2026-08-31
Rank Moved
Rank dropped 10 spots (#81 → #91)
GitHub → Website → npm: cloakbrowser-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 83.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/cloakbrowser-mcp.svg)](https://hvtracker.net/agents/cloakbrowser-mcp)
HTML:
<a href="https://hvtracker.net/agents/cloakbrowser-mcp"><img src="https://hvtracker.net/badge/cloakbrowser-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