Verified Repo Memory
Related Servers
Alternatives to Verified Repo Memory
No user-submitted related servers found.
Related Servers
- AlicenseBqualityNot gradedmaintenanceProvides repository-scoped safe memory for AI coding agents with just-in-time verification against file changes to ensure facts remain accurate. It links memories to specific code citations and automatically marks them as stale if the underlying source code is modified or deleted.5-
- AlicenseNot gradedqualityAmaintenanceProvides persistent memory for coding agents and grounds their claims by verifying against the actual codebase, preventing hallucinated responses.506 npmApache 2.0
- -licenseBqualityNot gradedmaintenanceA memory system for AI coding tools that stores and retrieves codebase context with project isolation. Enables coding assistants to maintain searchable memory of code snippets, comments, and runtime traces with full source traceability.2756 npm-
- FlicenseNot gradedqualityAmaintenancePersistent memory for AI coding agents: local-first semantic search, dependency graphs, git history.1-
- AlicenseNot gradedqualityAmaintenancePersistent memory for AI coding agents that knows when it has gone stale.3MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first evidence-backed repository memory for coding agents, providing read-only tools to list concepts, explain them, get governed context packs, and verify claims against the codebase.11Apache 2.0
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.