Is Bhived MCP safe to use?

Bhived MCP has an HVTrust score of 53.1/100 (Grade C), ranked #922 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Bhived MCP?

Bhived MCP scores 53.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 35 GitHub stars and is categorized under MCP Servers.

Bhived MCP

Repository Website

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.

MCP Servers TypeScript Listed Apache-2.0

Is Bhived MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.0 / 10

Provenance None

Signed commits 0%

Last push 2d ago

Advisories None known

Compare Bhived MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Bhived MCP scores 53.1/100 (Grade C), ranked #922 of 1374 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 4.0/10; recent commits are unsigned; no published advisory affects its latest release (bhived-mcp); last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Bhived MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 67.8 B · #252 of 778
Raise the OSSF Scorecard from 4.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +10.4 → 63.5 C · #329 of 778
Sign every commit0% signed today +5.0 → 58.1 C · #410 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Bhived MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Unsigned

github.com/ArtKeyAi/bhived-mcp, Apache-2.0, last pushed 2026-11-08. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0
Published packages Linked, not attested
- npm bhived-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: bhived-mcp 1.4.2. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-09-01 OSSF Scorecard: 2.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Bhived MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Bhived MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Bhived MCP’s 53.1.

Where the 53.1 comes from

HVTrust dimensions vs the MCP Servers average

53.1 / 100 · 100.0% confidence

Bhived MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.0 / 25

5.8 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

11.9 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

13.8 / 20

1.6 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.4 / 20

in line with avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-07

Rank Moved

Rank dropped 23 spots (#905 → #928)

2026-11-06

Rank Moved

Rank rose 29 spots (#934 → #905)

2026-11-06

Activity Score Changed

Activity score down 6pts (54 → 48)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent View MCP Servers Report missing data

48.3

Activity sub-score · out of 100

#511

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-08

2 days ago

Commits (4 wk)

Downloads (7d)

568

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #920

Analysis

Activity Inputs

48.3 / 100

StarsRepository reach

9.3 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

11.9 / 25

CommunityFork signal

2.2 / 20

Common questions about Bhived MCP

Public trust evidence for Bhived MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Bhived MCP publish package provenance?

No published build provenance is currently detected for Bhived MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Bhived MCP have an OpenSSF Scorecard?

Bhived MCP has an OpenSSF Scorecard score of 4.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Bhived MCP actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does Bhived MCP use?

Bhived MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Bhived MCP's commits signed?

0% of the last 100 commits to Bhived MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

high confidence

Implemented

Bhived MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

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.

2026-11-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-11-03

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-07

Rank Moved

Rank dropped 23 spots (#905 → #928)

2026-11-06

Rank Moved

Rank rose 29 spots (#934 → #905)

2026-11-06

Activity Score Changed

Activity score down 6pts (54 → 48)

2026-11-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-11-03

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-11-03

Rank Moved

Rank rose 44 spots (#985 → #941)

2026-11-03

Activity Score Changed

Activity score up 5pts (48 → 53)

2026-10-19

Rank Moved

Rank dropped 10 spots (#944 → #954)

2026-10-18

Rank Moved

Rank dropped 34 spots (#910 → #944)

2026-10-17

Rank Moved

Rank dropped 13 spots (#897 → #910)

2026-10-15

Rank Moved

Rank dropped 12 spots (#880 → #892)

2026-10-10

Rank Moved

Rank rose 30 spots (#887 → #857)

2026-10-09

Rank Moved

Rank rose 49 spots (#936 → #887)

2026-10-07

Grade Changed

Trust grade D → C

2026-10-07

Rank Moved

Rank rose 233 spots (#1169 → #936)

2026-10-07

HVTrust Changed

HVTrust up 10.4pts (40.6 → 51.0)

2026-10-07

Activity Score Changed

Activity score up 27pts (25 → 52)

2026-10-03

Rank Moved

Rank dropped 11 spots (#1151 → #1162)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 107 spots (#1226 → #1119)

2026-09-23

HVTrust Changed

HVTrust up 24.9pts (17.3 → 42.2)

2026-09-22

Newly Listed

First tracked at rank #1226

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 16 spots (#1099 → #1115)

2026-09-09

Rank Moved

Rank dropped 15 spots (#1079 → #1094)

2026-09-08

Rank Moved

Rank dropped 14 spots (#1065 → #1079)

2026-09-07

Rank Moved

Rank dropped 36 spots (#1029 → #1065)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1013 → #1029)

2026-09-05

Rank Moved

Rank rose 223 spots (#1236 → #1013)

2026-09-05

HVTrust Changed

HVTrust up 14.7pts (28.9 → 43.6)

2026-09-04

Rank Moved

Rank dropped 15 spots (#1221 → #1236)

2026-09-03

Rank Moved

Rank dropped 44 spots (#1177 → #1221)

2026-09-02

Rank Moved

Rank dropped 339 spots (#838 → #1177)

2026-09-02

HVTrust Changed

HVTrust down 14.7pts (43.8 → 29.1)

2026-09-01

Scorecard Added

OSSF Scorecard: 2.1/10

2026-09-01

Rank Moved

Rank rose 267 spots (#1105 → #838)

2026-09-01

HVTrust Changed

HVTrust up 15.8pts (28.0 → 43.8)

2026-08-31

Rank Moved

Rank rose 157 spots (#1262 → #1105)

2026-08-31

HVTrust Changed

HVTrust up 10.2pts (17.8 → 28.0)

2026-08-30

Rank Moved

Rank dropped 237 spots (#1025 → #1262)

2026-08-30

HVTrust Changed

HVTrust down 10.3pts (28.1 → 17.8)

2026-08-29

Rank Moved

Rank dropped 52 spots (#973 → #1025)

2026-08-28

Rank Moved

Rank dropped 37 spots (#936 → #973)

2026-08-27

Rank Moved

Rank dropped 24 spots (#912 → #936)

2026-08-26

Rank Moved

Rank dropped 112 spots (#800 → #912)

2026-08-24

Rank Moved

Rank rose 381 spots (#1177 → #796)

2026-08-24

HVTrust Changed

HVTrust up 10.5pts (17.9 → 28.4)

2026-08-22

Rank Moved

Rank dropped 375 spots (#798 → #1173)

2026-08-22

HVTrust Changed

HVTrust down 10.5pts (28.5 → 18.0)

2026-08-19

Rank Moved

Rank rose 372 spots (#1172 → #800)

2026-08-19

HVTrust Changed

HVTrust up 10.4pts (18.1 → 28.5)

2026-08-17

Rank Moved

Rank dropped 378 spots (#796 → #1174)

2026-08-17

HVTrust Changed

HVTrust down 10.6pts (28.7 → 18.1)

2026-08-16

Rank Moved

Rank dropped 17 spots (#779 → #796)

2026-08-13

Rank Moved

Rank rose 346 spots (#1125 → #779)

2026-08-13

HVTrust Changed

HVTrust up 10.1pts (18.8 → 28.9)

GitHub → Website → npm: bhived-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/bhived-mcp.svg)](https://hvtracker.net/agents/bhived-mcp)
            
HTML:
            <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

Data sources
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.4 · Raw JSON

Bhived MCP

How Bhived MCP could raise its score

Chain of custody

Source Unsigned

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Bhived MCP compares in MCP Servers

Where the 53.1 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Bhived MCP

AI agent surface

Maintain Bhived MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers