Glovebox MCP
Sandboxed computer-use MCP — drive a real browser + desktop apps in a nested X11 window.
Is Glovebox MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Glovebox MCP
How does it stack up against its MCP Servers neighbours?
- MCP Server for Binge-watch +0.3 higher
- Aigroup Mdtoword MCP +0.3 higher
- Airflow MCP Server same score
In detail: Glovebox MCP scores 37.2/100 (Grade D), ranked #1210 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.1/10; recent commits are unsigned; last pushed 2026-07-07. Every point is earned from checkable signals — never paid placement. How scoring works →
How Glovebox MCP compares in MCP Servers
- #720 MCP Server for Binge-watch 37.5 +0.3
- #721 Aigroup Mdtoword MCP 37.5 +0.3
- #722 Glovebox MCP 37.2 this agent
- #723 Airflow MCP Server 37.2 ±0
- #724 JustCall MCP Server 36.9 −0.3
Bars show each HVTrust score; the tick marks Glovebox MCP’s 37.2.
Where the 37.2 comes from
HVTrust dimensions vs the MCP Servers average
37.2 / 100 · 100.0% confidenceGlovebox 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
20.7 / 100Supply Chain Trust
Common questions about Glovebox MCP
Does Glovebox MCP publish package provenance?
Does Glovebox MCP have an OpenSSF Scorecard?
Is Glovebox MCP actively maintained?
What license does Glovebox MCP use?
Are Glovebox 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 Glovebox 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 Glovebox MCP?
For maintainers
HVTrust scores Glovebox 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/glovebox-mcp)
<a href="https://hvtracker.net/agents/glovebox-mcp"><img src="https://hvtracker.net/badge/glovebox-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