Memory Arbiter MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 11 Oct 2026.
Local SQLite MCP memory: evidence-based recall, advisory conflict notices, authorized governance.
What the code does
We read the source, 1 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, check=False, capture_output=True, text=True, timeout=600)
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 Memory Arbiter MCP
same job, measured the same wayEvidence-tracked local memory MCP server: one SQLite file; corrections retire dependent memories.
MCP server for Ordali memory: SQLite-backed project memory and governance traces.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
Shared local memory for coding agents: SQLite, semantic recall, linked entities, code navigation.
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.
Skill memory for coding agents: learn, recall, reinforce, decay. Local SQLite, no API key.
Portable agent memory anchored on Solana. Local SQLite + vector recall, open export.
Local-first agent memory over SQLite: remember, recall, link, forget. Degrades, never fails.
Memory Arbiter MCP — questions
Answers built from our own checks of this server.