memtrust
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZEP_API_KEY | No | API key for Zep (required to run the zep backend). | |
| MEM0_API_KEY | No | API key for the Mem0 hosted platform (required to run the mem0 backend). | |
| OPENAI_API_KEY | No | OpenAI API key used by mem0_direct for embeddings and extraction. | |
| OPENVIKING_API_KEY | No | API key for OpenViking (required to run the openviking backend). | |
| MEMPALACE_STORAGE_PATH | No | Path to the MemPalace storage (required to run the mempalace backend). | |
| MEMTRUST_JUDGE_API_KEY | No | API key for the LLM judge used in LongMemEval/LoCoMo evals (needed for LLM-judged evals). | |
| MEM0_DIRECT_VECTOR_STORE_URL | No | URL for the vector store, default is http://localhost:6333. | |
| MEM0_DIRECT_EMBEDDER_PROVIDER | No | Embedder provider for the mem0_direct backend (e.g., openai). | |
| MEM0_DIRECT_VECTOR_STORE_PROVIDER | No | Vector store provider for the mem0_direct backend (e.g., qdrant). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runA | Runs memtrust's agent-memory benchmark suite (LongMemEval, LoCoMo, contradiction-detection, and a dozen other evals) against one or more configured memory backends -- MemPalace, Mem0, Zep/Graphiti, OpenViking -- and returns the resulting JSON report. Call this when an agent needs a fresh, reproducible comparison of memory-backend quality or performance rather than trusting a vendor's self-reported numbers; do not call it just to read documentation (pass Behavior: this shells out to the real Parameter:
Return shape: on success, the parsed contents of memtrust's JSON report file (per-backend, per-eval results and scores -- see |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of ambiguity or misselection. The tool's purpose is clearly defined and distinct from any other tool because none exist.
The lone tool name 'run' is a clear verb that matches its action. While there is no pattern to compare against, the naming is consistent and intuitive for the single operation it performs.
The server has exactly one tool, which is appropriate for its focused purpose of running a benchmark suite. Although the count is minimal, it fully covers the server's intended functionality without unnecessary bloat.
The tool covers the core operation of running benchmarks, but lacks separate tools for inspecting existing reports or listing backends/evals. These gaps are partially mitigated by the ability to pass '--help' and use the CLI's subcommands, but the MCP surface itself is limited to a single action.