Bhived MCP
bhived is an MCP server that gives AI agents shared memory, skills, and tool discovery. install once, works in Claude Code, Cursor, and 15+ other agents.
Is Bhived MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Bhived MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Bhived MCP scores 42.1/100 (Grade D), ranked #1126 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.0/10; recent commits are unsigned; last pushed 2026-07-14. Every point is earned from checkable signals — never paid placement. How scoring works →
How Bhived MCP compares in MCP Servers
- #662 Gate DEX MCP 42.1 ±0
- #663 Sperax Crypto MCP 42.1 ±0
- #664 Bhived MCP 42.1 this agent
- #665 Hermes Atlas MCP 42.0 −0.1
- #666 Ejentum MCP 41.9 −0.2
Bars show each HVTrust score; the tick marks Bhived MCP’s 42.1.
Where the 42.1 comes from
HVTrust dimensions vs the MCP Servers average
42.1 / 100 · 100.0% confidenceBhived 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 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
26.4 / 100Supply Chain Trust
Common questions about Bhived MCP
Does Bhived MCP publish package provenance?
Does Bhived MCP have an OpenSSF Scorecard?
Is Bhived MCP actively maintained?
What license does Bhived MCP use?
Are Bhived 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 Bhived 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 Bhived MCP?
For maintainers
HVTrust scores Bhived 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/bhived-mcp)
<a href="https://hvtracker.net/agents/bhived-mcp"><img src="https://hvtracker.net/badge/bhived-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