Stealth Browser MCP
The only browser automation that bypasses anti-bot systems. AI writes network hooks, clones UIs pixel-perfect via simple chat.
Is Stealth Browser MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Stealth Browser MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Stealth Browser MCP scores 54.0/100 (Grade C), ranked #820 of 1325 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; 20% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Stealth Browser MCP compares in MCP Servers
- #459 RU Marketplace MCP 54.0 ±0
- #460 SeedanceMCP 54.0 ±0
- #461 Stealth Browser MCP 54.0 this agent
- #462 SharePoint MCP Server 54.0 ±0
- #463 Genieacs MCP 53.9 −0.1
Bars show each HVTrust score; the tick marks Stealth Browser MCP’s 54.0.
Where the 54.0 comes from
HVTrust dimensions vs the MCP Servers average
54.0 / 100 · 100.0% confidenceStealth Browser MCP MCP Servers average (775 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
72.4 / 100Supply Chain Trust
Common questions about Stealth Browser MCP
Does Stealth Browser MCP publish package provenance?
Does Stealth Browser MCP have an OpenSSF Scorecard?
Is Stealth Browser MCP actively maintained?
What license does Stealth Browser MCP use?
Are Stealth Browser MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/stealth-browser-mcp)
<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
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