hive-mind (toml0006/hive-mind) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
10 days ago

hive-mind

Enables coding agents to record, recall, supersede, and trace temporal decisions with rationale using MCP tools.

→ toml0006/hive-mind· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

toml0006

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: NEO4J_PASSWORD. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: NEO4J_PASSWORD, HIVE_MIND_NEO4J_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCODEX_SANDBOX
configHIVE_MIND_ACTORAttribution on confirmed decisions
configMINIFLARE_REGISTRY_PATH
configNEO4J_HTTP_URLWeb server Neo4j endpoint
🔐 secretNEO4J_PASSWORDWeb server Neo4j password
configNEO4J_USERWeb server Neo4j user
configWRANGLER_LOG_PATH
configWRANGLER_WRITE_LOGS
configHIVE_MIND_STATE_DIR
configHIVE_MIND_REPO_MAP~/.config/hive-mind/repos.yaml or set to an explicit
configXDG_CONFIG_HOME
configHIVE_MIND_PRACTICE_GROUPShared practice-memory group
configHIVE_MIND_GRAPHITI_FACTORYOptional semantic client factory
🔐 secretHIVE_MIND_NEO4J_PASSWORDPython Neo4j password
configHIVE_MIND_NEO4J_URIPython Neo4j connection
configHIVE_MIND_NEO4J_USERPython Neo4j user
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

8/8 tools missing one or more hints — why (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall_decisions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (NEO4J_PASSWORD → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/toml0006/hive-mind)](https://m8ven.ai/mcp/toml0006/hive-mind)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a964625eb8176410ca8c76ffe8d9d0919ca48f25
code hash: 1081924d0c4983d27152b5bcf78a5dc708df08b9e7105e7bb62a8cf4791f5169
verified: 9/2/2026, 8:01:59 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client