Memtrust MCP Server
Agent memory backends each publish their own benchmark numbers, on different tests, measured different ways. memtrust runs the same evals against all four and publishes the raw logs. Run against the vendors, not by them. It runs locally over stdio via the published package.
People who work with agent memory, benchmark and contradiction detection and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Python.
VERIFIED ACTIVE
LAST COMMIT 2026-08-25 · ★ 2 · #168 OF 304 MAINTAINED MEMORY · VERIFIED 2026-09-18
Apache-2.0 · Python servers · how we verify → /methodology
01 · Install Memtrust
before you install - you'll need
Set MEM0_API_KEY, ZEP_API_KEY, OPENVIKING_API_KEY, MEMPALACE_STORAGE_PATH, MEMTRUST_JUDGE_API_KEY before connecting.
Claude Code
claude mcp add rudrendupaul-memtrust -- uvx memtrust-cli Claude Desktop / Cursor / VS Code - add to config
{
"mcpServers": {
"rudrendupaul-memtrust": {
"command": "uvx",
"args": [
"memtrust-cli"
]
}
}
} Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.
Using another client? Same JSON, different key
Claude Desktop · mcpServers
Cursor · mcpServers
VS Code · servers
Windsurf · mcpServers
Zed · context_servers
Cline · mcpServers
Roo Code · mcpServers
Continue · mcpServers
LibreChat · mcpServers
Gemini CLI · mcpServers
Codex CLI · mcp_servers
Full setup guides: every client.
02 · Evidence
Security posture
What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.
runs as local process (stdio) - runs on your machine with your user's permissions
license Apache-2.0 - declared in the repository
pypi package memtrust-cli - check the name against the project README before installing (PyPI has no namespace ownership)
registry namespace io.github.RudrenduPaul is GitHub-verified and matches the repo owner
03 · What Memtrust can do
Prose above is summarized from the project's README and registry record - no invented capabilities.
Limitations (from the README)
[!WARNING] A real bug this run surfaced in mem0ai itself, not in memtrust: a fresh mem0ai==2.0.12 install with nothing but OPENAI_API_KEY set fails every single LLM-based extraction call, out of the box, for anyone.
Latest releases
v0.3.3 · 2026-07-21
Fixes the memtrust mirror package's version bug (0.3.2 only fixed memtrust-cli, not memtrust -- the version lookup now tries both distribution names), a --eval help-text drift bug (was still missing…
v0.3.2 · 2026-07-20
Fixes the memtrust --version bug (was always printing 0.0.0+unknown), wires the temporal-KG boundary eval into the CLI, and ships the project's first live benchmark result (mem0_direct, self-hosted mem0ai) along with a…
v0.3.1 · 2026-07-19
Docs sync: README FAQ additions.
04 · Who maintains Memtrust
memtrust is maintained by rudrendupaul. We track 35 MCP servers from rudrendupaul - 35 actively maintained, 6 combined GitHub stars, oldest repo from Mar 2026.
05 · Facts
- repository
- github.com/rudrendupaul/memtrust
- category
- memory - ranked #168 of 304 actively-maintained memory servers as of 2026-09-18.
- release cadence
- 5 releases in the last 90 days (latest 2026-07-21)
- registry
- io.github.RudrenduPaul/memtrust (active, first published 2026-08-10)
- packages
- pypi:memtrust-cli
06 · Memtrust FAQ
What is Memtrust?
Agent memory backends each publish their own benchmark numbers, on different tests, measured different ways. memtrust runs the same evals against all four and publishes the raw logs. Run against the vendors, not by them. It runs locally over stdio via the published package.
Is Memtrust still maintained?
Yes - as of 2026-09-18, its last commit was 2026-08-25 and it shipped 5 releases in the last 90 days. We re-verify nightly.
How do I install Memtrust?
Run `uvx memtrust-cli`. The README documents 5 environment variables (MEM0_API_KEY, ZEP_API_KEY, OPENVIKING_API_KEY…) to set first. Set MEM0_API_KEY, ZEP_API_KEY, OPENVIKING_API_KEY, MEMPALACE_STORAGE_PATH, MEMTRUST_JUDGE_API_KEY before connecting. You can also paste the ready-made client config above.
Does Memtrust run locally?
Yes - it's a stdio server: it runs on your machine (via uvx) with your user's permissions. Your data stays local unless the server itself calls external APIs.
07 · Alternatives to Memtrust
Alternatives to Memtrust
Maintained memory servers if Memtrust isn't the fit.
- Codebase Memory Codebase knowledge graph for AI agents - 162 languages, sub-ms queries, 99% fewer tokens. ★ 43,715 · 2026-09-18
- Superlog Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents. ★ 1,449 · 2026-09-17
- Tradememory Protocol Tamper-evident decision audit trail and outcome-weighted memory for AI trading agents. ★ 1,419 · 2026-09-14
- Persome Local-first personal memory and model server for trusted MCP agents on macOS. ★ 1,322 · 2026-08-21
- Neo4j Memory MCP Neo4j Knowledge Graph Memory Server ★ 984 · 2026-09-09
- Projectmem Coding agent memory - one local MCP server for every project. Warns before repeating failed fixes. ★ 826 · 2026-09-15
Pairs well with
Servers that cover what Memtrust doesn't - only shown when the pairing reason fits the companion.
More memory MCP servers · Norn · Vestige · World Model MCP · Perenna · Filamental
More Python MCP servers · Agent Wormhole · Orchestrator · Xlsx Tools MCP · Hermes Grocy MCP · wallabag MCP · see all