# io.github.Bumblebiber/hmem-mcp

Persistent 5-level hierarchical memory for AI agents. SQLite-backed, lazy-loaded.

- **Type:** MCP server
- **Trust:** 40/100 (C), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.6.7
- **Author:** io.github.Bumblebiber
- **License:** Unknown
- **npm:** hmem-mcp
- **Source:** https://github.com/Bumblebiber/hmem
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

40/100 (C), scored on the package rubric
- Publisher verified: no
- Install scripts: suspicious script found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 116 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** warnings
- **Scanned:** 2026-06-13T09:10:38.698Z
- **Version scanned:** 7.4.1
- **CVEs:** none found by OSV at scan time
**Findings**
- install script `postinstall`: child_process module access

## Tools

23 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `update_many`
- `reset_memory_cache`
- `export_memory`
- `import_memory`
- `memory_stats`
- `memory_health`
- `tag_bulk`
- `tag_rename`
- `move_memory`
- `rename_id`
- `move_nodes`
- `search_memory`
- `write_memory`
- `update_memory`
- `flush_context`
- `append_memory`
- `read_memory`
- `find_related`
- `load_project`
- `read_project`
- `create_project`
- `list_projects`
- `set_active_device`

## Install

**Verdict: review** — Installable, but 3 things to check first: 1 npm lifecycle script flagged — these run on `npm install`, before the server is ever started.
**Cautions** (coverage gaps and advisories — never blocking)
- 1 npm lifecycle script flagged — these run on `npm install`, before the server is ever started. — postinstall: child_process module access
- The last scan is 116 days old — the evidence behind this verdict is dated.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"hmem\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"hmem-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on your machine.
- Floor 38, ceiling 62 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.Bumblebiber%2Fhmem-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.Bumblebiber%2Fhmem-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.Bumblebiber%2Fhmem-mcp
- HTML page: https://forgeregistry.com/registry/io.github.Bumblebiber%2Fhmem-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.