Cognitive AI Memory runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 14 Jul 2026.
Ebbinghaus-based persistent memory for Claude. Memories decay with time, strengthen on recall.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
result = subprocess.run(cmd, capture_output=True, text=True)
fp = os.path.join(tmp, f"f{i:04d}.gif")
return pickle.load(f)
document.getElementById('nBody').innerHTML = body;
env = dict(os.environ)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Cognitive AI Memory
same job, measured the same wayPersistent memory for AI agents. Memories decay with time and strengthen on recall.
Persistent cross-platform memory for AI agents with Ebbinghaus decay scoring.
Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.
Persistent, read-only codebase memory for Claude Code; ask it instead of re-reading files.
Persistent memory for Claude Code. Search, recall, and re-inject context from any session.
Persistent AI memory with semantic search, conflict detection, and ticketing.
Persistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients.
Shared, persistent memory for AI agents — works with Claude, Kiro, Cursor, or any MCP client.
Cognitive AI Memory — questions
Answers built from our own checks of this server.