Sauce Api MCP
MCP Server that models the Sauce Labs API
Is Sauce Api MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Sauce Api MCP
How does it stack up against its MCP Servers neighbours?
- Webcomponents MCP Server +0.1 higher
- Codex Control Plane MCP +0.1 higher
- Azure DevOps (ADO) 0.1 lower
In detail: Sauce Api MCP scores 67.1/100 (Grade B), ranked #399 of 1325 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 4.9/10; 62% of recent commits are signed; last pushed 2026-09-18. Every point is earned from checkable signals — never paid placement. How scoring works →
How Sauce Api MCP compares in MCP Servers
- #236 Webcomponents MCP Server 67.2 +0.1
- #237 Codex Control Plane MCP 67.2 +0.1
- #238 Sauce Api MCP 67.1 this agent
- #239 Azure DevOps (ADO) 67.0 −0.1
- #240 MCP Server for WinDbg Crash Analysis 67.0 −0.1
Bars show each HVTrust score; the tick marks Sauce Api MCP’s 67.1.
Where the 67.1 comes from
HVTrust dimensions vs the MCP Servers average
67.1 / 100 · 100.0% confidenceSauce Api 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
40.9 / 100Supply Chain Trust
Common questions about Sauce Api MCP
Does Sauce Api MCP publish package provenance?
Does Sauce Api MCP have an OpenSSF Scorecard?
Is Sauce Api MCP actively maintained?
What license does Sauce Api MCP use?
Are Sauce Api 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 Sauce Api 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 Sauce Api MCP?
For maintainers
HVTrust scores Sauce Api 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/sauce-api-mcp)
<a href="https://hvtracker.net/agents/sauce-api-mcp"><img src="https://hvtracker.net/badge/sauce-api-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON