memlikehuman@0.2.0
VERIFIED· startup onlyPublisher claims: "A local Python + SQLite MCP memory service that stores persona, shared experiences, facts, agreements, and unfinished work, then restores them within a context budget so a new model can continue the same conversation. It supports offline original-text persistence, Chinese keyword retrieval, provenance-tracked memories, persona versioning/rollback, and progressive fading of older events." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
GITHUB_TOKENMEMLIKEHUMAN_API_KEYConfiguration, not credentials: DSH_HOME, GITHUB_REPOSITORY, MEMLIKEHUMAN_HOME, MLH_SMOKE_REPORT- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for GITHUB_TOKEN, MEMLIKEHUMAN_API_KEY and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-13 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 20 s · 2 scenariosStatic findings
child = subprocess.run([sys.executable, "-c", code, str(data)], check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.ProviderConfig(base_url="https://user:[email protected]/v1")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.