Verified Repo Memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vrm_storeB | Store a memory with file citations. Snippets are auto-extracted. |
| vrm_searchC | Search for candidates (no JIT verification, fast). |
| vrm_retrieveC | JIT-verify candidates and return valid memories. |
| vrm_listC | List memories by status. |
| vrm_forgetA | Manually delete a memory by ID. |
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 5 tools
Each tool targets a distinct action: store (add), search (find candidates quickly), retrieve (verify and return valid memories), list (enumerate by status), forget (delete). The boundaries are clear, especially with the verification distinction between search and retrieve.
All tool names follow the consistent pattern 'vrm_' prefix plus an imperative verb (store, search, retrieve, list, forget). This is a uniform, predictable convention that makes the tool set easy to navigate.
With exactly 5 tools, the server covers the core memory lifecycle (create, read, list, delete) without bloat. Each tool earns its place, and the scope is well-matched to the stated purpose.
The set covers the essential operations for a memory store: add, search, retrieve, list, and forget. However, there is no update operation, and retrieval is tied to verification rather than direct ID lookup, which could be a minor gap for some workflows.