hmem (bumblebiber/hmem) is an MCP server listed on the M8ven Trust Index. It scores 67 out of 100, grade C. It declares 26 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
67/100

hmem

Hierarchical persistent memory for AI agents with automatic summarization and context retrieval.

→ bumblebiber/hmem· listed on pulsemcp

Caution. Specific findings reduced this grade. They are listed on the page. 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

bumblebiber

Source: PulseMCP

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

PulseMCPnot 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: OPENAI_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
🔐
You'll be asked for 3 credentials: CODEX_API_KEY, DEEPSEEK_API_KEY, OPENAI_API_KEY
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.
configCLAUDECODE
configCLAUDE_CODE_SESSION_ID
🔐 secretCODEX_API_KEY
configCODEX_SESSION_ID
🔐 secretDEEPSEEK_API_KEY"checkpointApiKeyEnv": ""
configHMEM_ACTIVE_PROJECT
configHMEM_DEPTH
configHMEM_HARNESS
configHMEM_NO_SESSIONE Error 158 spurious O-entries created when Haiku MCP lacked guard
configHMEM_PATH"": "C:/Users/YOUR_USERNAME/.hmem/Agents/DEVELOPER/DEVELOPER.hmem"
configHMEM_PROJECT_DIR"": "/home/yourname/.hmem",
configHMEM_SYNC_PASSPHRASEAdd to your MCP config for automatic sync on every read/write.
configLLM_MODEL
🔐 secretOPENAI_API_KEYcheckpointApiKeyEnv provider default Env var holding the API key. Defaults: ANTHROPIC_API_KEY or
configOPENAI_BASE_URL
configWSLENV
configWSL_DISTRO_NAME
// 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

26/26 tools missing one or more hints — update_many (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reset_memory_cache (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); export_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +23 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.

Destructive tools are labelled

6 tools perform destructive updates without destructiveHint — flush_context deletes at line 130 (fs.unlinkSync(CACHE_RESET_SIGNAL)); read_memory deletes at line 130 (fs.unlinkSync(CACHE_RESET_SIGNAL)); load_project deletes at line 130 (fs.unlinkSync(CACHE_RESET_SIGNAL))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

24/26 tool handlers declare input schemas (92%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

24/26 tool handlers wrap calls in try/catch (92%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 6/26 tools referenced in tests (23%)

Write tests that reference each tool by name so every tool has at least one test.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

5 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

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 9 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 Verified](https://m8ven.ai/badge/mcp/bumblebiber/hmem?variant=verified)](https://m8ven.ai/mcp/bumblebiber/hmem)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0ccb04f033d55dae49d3c7ba395aff473cd1b593
code hash: 3ca7e613a8dec681140e8a156931d63553e6dd93cc83f22e089aec8fcb3b2650
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