Bitrise
MCP Server for the Bitrise API, enabling app management, build operations, artifact management and more.
Is Bitrise safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Bitrise
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Bitrise scores 48.4/100 (Grade D), ranked #984 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.9/10; 31% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Bitrise compares in MCP Servers
- #572 App Publish MCP 48.5 +0.1
- #573 Meta Ads MCP 48.5 +0.1
- #574 Bitrise 48.4 this agent
- #575 Gemini MCP 48.4 ±0
- #576 One Search MCP 48.3 −0.1
Bars show each HVTrust score; the tick marks Bitrise’s 48.4.
Where the 48.4 comes from
HVTrust dimensions vs the MCP Servers average
48.4 / 100 · 100.0% confidenceBitrise 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
50.4 / 100Supply Chain Trust
Common questions about Bitrise
Does Bitrise publish package provenance?
Does Bitrise have an OpenSSF Scorecard?
Is Bitrise actively maintained?
What license does Bitrise use?
Are Bitrise'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 Bitrise'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 Bitrise?
For maintainers
HVTrust scores Bitrise 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/bitrise)
<a href="https://hvtracker.net/agents/bitrise"><img src="https://hvtracker.net/badge/bitrise.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