Verified Repo Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| repo | Yes | The absolute path to the repository. Memories are scoped per repository and stored in the <repoRoot>/.verified-repo-memory/ directory. | |
| no-secret-scan | No | If provided, disables the built-in heuristic secret scanning that rejects memories that look like API keys or private keys. |
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 has a clearly distinct purpose with no overlap: forget deletes, list enumerates, retrieve verifies and returns, search finds candidates, and store creates. The descriptions explicitly differentiate them, such as distinguishing retrieve (with JIT verification) from search (fast, no verification).
All tools follow a consistent 'vrm_' prefix and verb_noun pattern (e.g., vrm_forget, vrm_list, vrm_retrieve, vrm_search, vrm_store). This predictable naming makes it easy for agents to understand and select tools without confusion.
With 5 tools, the set is well-scoped for a memory management server, covering core operations like store, retrieve, search, list, and forget. Each tool earns its place, providing a complete yet manageable surface without bloat or thinness.
The tool surface offers complete CRUD/lifecycle coverage for memory management: store (create), retrieve/read (with verification), search (find), list (enumerate), and forget (delete). There are no obvious gaps, enabling agents to handle all typical workflows without dead ends.