memtrust
memtrust is an MCP server, listed under memory & vectors. It reaches mem0, memtrust, openviking and zep. It needs MEM0_API_KEY, MEMTRUST_JUDGE_API_KEY, OPENVIKING_API_KEY and ZEP_API_KEY to authenticate. Its repository has 2 GitHub stars and is licensed under Apache-2.0; we last read it on 2026-10-23.
It is a command-line interface for benchmarking agent-memory backends such as MemPalace, Mem0, Zep, and OpenViking, publishing raw evaluation logs.
Install
Read from memtrust’s own README, close to verbatim -- not written by us, and not guessed.
pip install memtrust-cli
What it reaches, and what it needs
Maintenance
Independent CLI benchmark harness for agent-memory backends (MemPalace, Mem0, Zep, OpenViking); publishes raw eval logs.
memtrust compared with similar servers
| Server | Reaches | Needs | Stars | Last update | Licence |
|---|---|---|---|---|---|
| memtrust (this page) | mem0, memtrust, openviking, zep | MEM0_API_KEY, MEMTRUST_JUDGE_API_KEY, OPENVIKING_API_KEY, ZEP_API_KEY | 2 | 2026-09-25 | Apache-2.0 |
| mem0-mcp | mem0, openai, supabase(1 shared) | MEM0_API_KEY, OPENAI_API_KEY, SUPABASE_KEY | 96 | 2026-10-21 | MIT |
| mcp-server-qdrant | qdrant | QDRANT_API_KEY | 1,553 | 2026-09-04 | Apache-2.0 |
| mcp-knowledge-graph | — | None listed | 886 | 2026-05-29 | MIT |
| chroma-mcp | chroma | CHROMA_API_KEY, CHROMA_CUSTOM_AUTH_CREDENTIALS | 601 | 2025-09-17 | Apache-2.0 |
| caura | — | None listed | 504 | 2026-10-25 | Apache-2.0 |
Ranked by services in common with memtrust, then by stars. Figures are from each repository when we last read it.
Common questions about memtrust
- What does memtrust do?
- It is a command-line interface for benchmarking agent-memory backends such as MemPalace, Mem0, Zep, and OpenViking, publishing raw evaluation logs.
- How do I install memtrust?
- Its own README gives this command: pip install memtrust-cli. Run it where your MCP client can launch the server, and check the README for any settings it asks for.
- What does memtrust connect to, and what does it need?
- It reaches mem0, memtrust, openviking and zep. The credentials we found in its source are MEM0_API_KEY, MEMTRUST_JUDGE_API_KEY, OPENVIKING_API_KEY and ZEP_API_KEY.
- Is memtrust official and is it maintained?
- We found nothing naming it as a vendor’s official server. Its repository has 2 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-09-25.
- What licence does memtrust use?
- The repository declares the Apache-2.0 licence.
More MCP servers for memory & vectors
- mcp-server-qdrant1,553 stars
- mcp-knowledge-graph886 stars
- chroma-mcp601 stars
- caura504 stars
- MemoryMesh354 stars
- neural-memory242 stars