knowmind runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 13 Sep 2026.
AI agent memory & knowledge graph, hosted in Germany (GDPR). Recall, relations, store via MCP.
What the code does
We read the source, 22 h ago · rules 3dff92dd89df
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.
const child = spawn(process.execPath, [self, "status", "--probe"], {
prozess = subprocess.Popen(
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 knowmind
same job, measured the same wayPersistent memory for AI agents. Store, recall, and share knowledge across sessions.
Persistent memory for AI agents. Remember, recall, and explore a shared knowledge graph.
Cross-agent memory over MCP: hybrid recall, knowledge graph, private/shared visibility, redaction.
Local-first knowledge engine for AI agents: memory, graph, and recall over MCP.
Hosted agent memory: store, search, and recall facts across sessions from any MCP client.
Graph-native memory for AI agents: a knowledge graph built from conversation, via MCP.
Knowledge-graph memory server for AI tools via MCP
Cognitive memory for AI agents — semantic recall, knowledge graph, and contradiction detection
knowmind — questions
Answers built from our own checks of this server.