memento-mcp@1.2.2
VERIFIED· not startedPublisher claims: "The Autonomous Nervous System for AI Agents — local-first MCP middleware with temporal graph memory, active coercion, and proactive goal alignment." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
MEMENTO_PROACTIVE_MAX_TOKENSMEMENTO_UI_AUTH_TOKENOPENAI_API_KEYConfiguration, not credentials: MEM0_EMBEDDING_MODEL, MEM0_MODEL, MEMENTO_AUTONOMY_INTERVAL, MEMENTO_DECAY_EPISODIC, MEMENTO_DECAY_SEMANTIC, MEMENTO_DECAY_WORKING, MEMENTO_DIR, MEMENTO_EMBEDDING_BACKEND, MEMENTO_FEDERATION_SOCKET, MEMENTO_HANDOFF_AUTO_CHECKPOINT_EVERY_N_EVENTS, MEMENTO_KG_DB_PATH, MEMENTO_LEDGER_COMPACT_AFTER, MEMENTO_LEDGER_QUIET, MEMENTO_PROACTIVE_INJECT, MEMENTO_PROACTIVE_STRATEGY, MEMENTO_PROACTIVE_TOP_K, MEMENTO_RULE_CONFIRMATION, MEMENTO_SHARED_KG_PATH, MEMENTO_SKIP_LEDGER_HOOK, MEMENTO_UI, MEMENTO_UI_PORT, MEMENTO_WRITE_SEARCH_TRACE, OPENAI_BASE_URL- 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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for MEMENTO_PROACTIVE_MAX_TOKENS, MEMENTO_UI_AUTH_TOKEN, OPENAI_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; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 82/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 · 0 s · 2 scenarios · 0 deviationsStatic findings
ALWAYS loaded. Keep under 500 chars. Critical discoveries only.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["git", "init", "-q"], cwd=tmp_path, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.User content. Never auto-pruned.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.return subprocess.run( # noqa: S603Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.check_output(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.log = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.repo_root = subprocess.check_output(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.log = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.check_output(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.help="Best-effort: kill running memento-mcp processes after update.",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.<summary>Running without OpenAI (offline / testing)</summary> Set `MEMENTO_EMBEDDING_BACKEND=none` to disable embeddings. Memento falls back to FTS5-only searchFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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
No advisories in OSV for memento-mcp@1.2.2 as of 3d ago. This is the package itself, not its dependencies.