io.github.Leonhest/hivemind
NPM · HIVEMIND-AGENTS
A shared, live plan for teams of coding agents, synced through your git remote.
Available components
Last scanned (1 hour ago)
Scores higher than 40% of npm servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 420 tokens (~52/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 24% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "contract_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +5
- Stability: unverified → 0.33 ▲ functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed npm/hivemind-agents@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
contract_publish ~111
Publish or change something other agents build against: an API route and its request/response shape, a DB schema, a shared type, an env var, or file ownership. Set breaking=true if existing consumers must change.
| Name | Type | Req | Description |
|---|---|---|---|
| areas | array | – | – |
| breaking | boolean | – | – |
| key | string | yes | Stable name, e.g. "POST /api/login" or "User" |
| spec | string | yes | The concrete shape, e.g. "{ id: uuid, email: string }" |
No output schema declared.
No examples provided.
decision_log ~44
Record a project decision teammates should follow (library choice, convention, architecture).
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| rationale | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
goal_set ~32
Set or change a project goal / scope statement.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
plan_get ~44
Read the team's shared plan: goals, contracts (APIs/schemas/types), decisions, tasks and open questions.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only return this kind of entry |
No output schema declared.
No examples provided.
plan_remove ~30
Remove an obsolete entry from the plan.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| kind | string | yes | – |
No output schema declared.
No examples provided.
question ~47
Ask the team an open question, or answer one (providing answer closes it for discussion).
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | – |
| key | string | yes | – |
| text | string | – | – |
No output schema declared.
No examples provided.
task_claim ~67
Claim a task so teammates know you are working on it. Call before starting a piece of work.
| Name | Type | Req | Description |
|---|---|---|---|
| areas | array | – | Files, directories or topics this task touches |
| key | string | yes | Short stable id, e.g. "auth-api" |
| title | string | yes | – |
No output schema declared.
No examples provided.
task_update ~45
Update a task: progress note, status change, or mark done/blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| note | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.Leonhest/hivemind MCP server?
io.github.Leonhest/hivemind runs locally as an npm package, launched with npx -y hivemind-agents. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · hivemind-agents
claude mcp add leonhest-hivemind -- npx -y hivemind-agents
What is the io.github.Leonhest/hivemind MCP server?
io.github.Leonhest/hivemind is an MCP server listed in the public MCP registry as io.github.Leonhest/hivemind. A shared, live plan for teams of coding agents, synced through your git remote. This page covers its npm package (hivemind-agents).
Is the io.github.Leonhest/hivemind MCP server safe to use?
io.github.Leonhest/hivemind scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Leonhest/hivemind MCP server expose?
io.github.Leonhest/hivemind exposes 8 tools: plan_get, task_claim, task_update, contract_publish, decision_log, and 3 more. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.
Is the io.github.Leonhest/hivemind MCP server still maintained?
io.github.Leonhest/hivemind is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Leonhest/hivemind MCP server under?
io.github.Leonhest/hivemind declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.