- Home
- MCP servers
- Verified Repo Memory
Verified Repo Memory
- typescript
1
GitHub Stars
typescript
Language
3 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"cognitivemyriad-mcp-verified-repo-memory": {
"command": "npx",
"args": [
"-y",
"@cognitivemyriad/vrm-local",
"--repo",
"/absolute/path/to/your/repo"
]
}
}
}You run a local MCP server that provides stale-proof, repository-scoped memories with file-backed citations and just-in-time verification. This enables safe memory delivery to AI coding agents, ensuring agents receive fresh, relevant information tied to the current state of your codebase.
How to use
You interact with the Verified Repo Memory MCP server through a local, stdio-based transport. The server is designed for use with MCP clients that support stdio connections, such as Claude Desktop or Claude Code, and it keeps memories tightly scoped to a specific repository.
How to install
Prerequisites: ensure you have Node.js and npm installed on your machine.
Step 1: Install and run the server via the quickstart command.
npx -y @cognitivemyriad/vrm-local --repo /path/to/repo
Step 2: Alternatively, you can build and run from source.
npm ci
npm run build
node build/index.js --repo /path/to/repo
Security and data handling
This server runs locally with no network transmissions. It avoids path traversal beyond the repository root and blocks access to sensitive directories. All logging is written to standard error, and built-in secret scanning helps reject memories that resemble API keys or private keys (this can be disabled with a dedicated flag when you start the server).
Usage notes and patterns
Memories are stored under a repository-scoped data directory to prevent cross-repo pollution. Citations link each memory to a specific file path and line range. The system verifies memories just-in-time before returning them to an agent, ensuring you don’t ship stale or relocated code snippets.
Notes for Claude integration
To connect the server to Claude Desktop or Claude Code, provide a stdio-based MCP configuration that launches the local server using the npm-published package.
Helpful usage examples
Store and verify memories through your MCP client, then retrieve only valid, up-to-date entries.”
Available tools
vrm_store
Store a new memory with file citations and optional subject and fact fields.
vrm_search
Search for candidate memories by keywords to locate relevant memories.
vrm_retrieve
JIT-verify candidate memories and return only valid ones to the agent.
vrm_list
List memories by status, such as valid, stale, or missing.
vrm_forget
Manually delete a memory from the storage.