Growthbook MCP
Official GrowthBook MCP server for creating flags, getting experiments, and more.
Is Growthbook MCP safe? Strong public trust posture, backed by multiple independent signals.
Compare Growthbook MCP
How does it stack up against its MCP Servers neighbours?
- Marketplaces MCP (RU) — Wildberries & Ozon same score
- LibreNMS MCP same score
- Filesystem MCP same score
In detail: Growthbook MCP scores 76.1/100 (Grade B), ranked #204 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 5.1/10; 25% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Growthbook MCP compares in MCP Servers
- #116 Marketplaces MCP (RU) — Wildberries & Ozon 76.1 ±0
- #117 LibreNMS MCP 76.1 ±0
- #118 Growthbook MCP 76.1 this agent
- #119 Filesystem MCP 76.1 ±0
- #120 ITASCA MCP Server 76.1 ±0
Bars show each HVTrust score; the tick marks Growthbook MCP’s 76.1.
Where the 76.1 comes from
HVTrust dimensions vs the MCP Servers average
76.1 / 100 · 100.0% confidenceGrowthbook 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
54.6 / 100Supply Chain Trust
Common questions about Growthbook MCP
Does Growthbook MCP publish package provenance?
Does Growthbook MCP have an OpenSSF Scorecard?
Is Growthbook MCP actively maintained?
What license does Growthbook MCP use?
Are Growthbook 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 Growthbook 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 Growthbook MCP?
For maintainers
HVTrust scores Growthbook 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/growthbook-mcp)
<a href="https://hvtracker.net/agents/growthbook-mcp"><img src="https://hvtracker.net/badge/growthbook-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON