@hiveai/mcp
hAIve MCP server — exposes memory + project context to any MCP-compatible AI client
12
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
sadydoucoure
Keywords
aienforcementpolicycontextbreadcrumbsmemorymcphaivemodel-context-protocolagentteamharnessharness-engineering
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Likely CI/publish environment change; publisher identity and repo URL are consistent across versions. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @hiveai/mcp package; edit-distance match to 'yup' is coincidental, not a real typosquat. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 0.2.10 | 3 / 0 | |
| 0.2.9 | 3 / 0 | |
| 0.2.8 | 3 / 0 | |
| 0.2.7 | 3 / 0 | |
| 0.2.6 | 3 / 0 | |
| 0.2.4 | 3 / 0 | |
| 0.2.3 | 3 / 0 | |
| 0.2.2 | 3 / 0 | |
| 0.2.1 | 3 / 0 | |
| 0.2.0 | 3 / 0 | |
| 0.1.1 | 3 / 0 | |
| 0.1.0 | 3 / 0 |
v0.2.10
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.