Stealth Browser MCP

The only browser automation that bypasses anti-bot systems. AI writes network hooks, clones UIs pixel-perfect via simple

MCP Servers Python Grade C Listed MIT
50.5/100
Rank #886 of 1328
Compare Stealth Browser MCP

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-09-07 · 1d ago
Recent change
Rank +10

Is Stealth Browser MCP safe? Stealth Browser MCP scores 50.5/100 (Grade C), ranked #886 of 1328 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.7/10; 15% of recent commits are signed; last pushed 2026-09-07. Every point is earned from checkable signals — never paid placement. How scoring works →

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-09-08
Rank Moved
Rank dropped 12 spots (#874 → #886)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank dropped 17 spots (#857 → #874)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
67.9
Activity sub-score · out of 100
#499

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-09-08 15:33 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
1.9k
Forks
274
Last Push
2026-09-07
yesterday
Commits (4 wk)
8?
Downloads (7d)
HN mentions (30d)
Open Issues
2
Rank Change
▼12
was #874

Analysis

HVTrust Dimensions vs MCP Servers

50.5 / 100 · 100.0% confidence

Stealth Browser MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.4 / 25
4.5 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
1.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.9 / 20
1.0 above avg 6.9

Activity Inputs

67.9 / 100
StarsRepository reach
19.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
11.3 / 20

Supply Chain Trust

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

Is Stealth Browser MCP safe?

Public trust evidence for Stealth Browser 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 Stealth Browser MCP publish package provenance?
No published build provenance is currently detected for Stealth Browser 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 Stealth Browser MCP have an OpenSSF Scorecard?
Stealth Browser MCP has an OpenSSF Scorecard score of 3.7/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 Stealth Browser MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Stealth Browser MCP use?
Stealth Browser MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Stealth Browser MCP's commits signed?
15% of the last 100 commits to Stealth Browser 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
Stealth Browser MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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
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 Stealth Browser 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-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Stealth Browser MCP?

For maintainers

HVTrust scores Stealth Browser 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.

Reputation Timeline

Signal history
Rank 17Grade 3Score 2HVTrust 2Listed 1Scorecard 1Surface 1
2026-09-08
Rank Moved
Rank dropped 12 spots (#874 → #886)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank dropped 17 spots (#857 → #874)
2026-09-06
Rank Moved
Rank dropped 15 spots (#842 → #857)
2026-09-05
Rank Moved
Rank dropped 62 spots (#780 → #842)
2026-09-04
Grade Changed
Trust grade C → D
2026-09-04
Rank Moved
Rank dropped 30 spots (#750 → #780)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-03
Rank Moved
Rank dropped 100 spots (#650 → #750)
2026-09-02
Rank Moved
Rank dropped 14 spots (#636 → #650)
2026-09-01
Rank Moved
Rank dropped 22 spots (#614 → #636)
2026-08-31
Rank Moved
Rank dropped 34 spots (#580 → #614)
2026-08-29
Rank Moved
Rank dropped 14 spots (#560 → #574)
2026-08-28
Grade Changed
Trust grade D → C
2026-08-28
Rank Moved
Rank rose 60 spots (#620 → #560)
2026-08-28
HVTrust Changed
HVTrust up 4.2pts (46.1 → 50.3)
2026-08-28
Activity Score Changed
Activity score up 11pts (51 → 62)
2026-08-27
Rank Moved
Rank dropped 12 spots (#608 → #620)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.2/10
2026-08-26
Rank Moved
Rank rose 433 spots (#1041 → #608)
2026-08-26
HVTrust Changed
HVTrust up 25.5pts (20.6 → 46.1)
2026-08-23
Rank Moved
Rank dropped 52 spots (#981 → #1033)
2026-08-23
Activity Score Changed
Activity score down 8pts (59 → 51)
2026-08-22
Rank Moved
Rank rose 10 spots (#991 → #981)
2026-08-17
Rank Moved
Rank rose 12 spots (#988 → #976)
2026-08-16
Rank Moved
Rank dropped 28 spots (#960 → #988)
2026-08-10
Newly Listed
First tracked at rank #952

Embed Badge Badge guide for maintainers →

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