verifiable-memory
Related Servers
Alternatives to verifiable-memory
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceProvenance-first agent memory MCP server with a real corrections API (assert/retract/supersede with tombstones) and a one-command junk audit for memory stores.51MIT

dakera-mcpofficial
AlicenseAqualityCmaintenanceSelf-hosted MCP-native agent memory server. Gives AI agents persistent, decay-weighted memory via 83 MCP tools — no cloud, full control. RocksDB+HNSW backend. Works with Claude Code, Cursor, and any MCP-compatible agent.149MIT- AlicenseAqualityBmaintenanceAn MCP server that gives AI agents durable, temporal memory over local markdown vaults, with tools for searching, asserting facts, querying point-in-time state, and reinforcing useful knowledge.15167 npmMIT
- AlicenseAqualityCmaintenanceLocal-first, source-traceable memory for AI agents — no LLM at ingest, $0 per message, zero data egress. Gives Claude Code, Cursor, and any MCP client one shared persistent memory with semantic recall, belief revision, selective forgetting, and a provenance guard that blocks acting on stale or unconfirmed memories.2319 PyPI14MIT
- FlicenseAqualityAmaintenanceLocal-first agent-memory MCP server with a why() tool: recall a fact together with its connected subgraph (multi-hop), so linked memories surface even when they share no words with the query. remember/recall/relate/forget/why over one fused vector + graph + columnar engine a single offline Rust binary.8102-
- AlicenseCqualityAmaintenanceLocal-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.4033 PyPI1MIT
TDQS
Scored across 13 tools
Every tool has a clearly distinct purpose: storing (learn_fact), recalling (recall), updating (update_fact), deleting (forget), auditing (history, contradictions), proving (prove_fact, verify_proof, verify_receipt), and traversing (multihop, all_paths). No two tools overlap in functionality.
All tool names use consistent snake_case with a verb_noun pattern (e.g., learn_fact, update_fact, prove_fact) or noun_verb (knowledge_root, verify_receipt). The naming is predictable and intuitive.
With 13 tools, the server covers the essential operations for a verifiable memory system without being excessive. Each tool justifies its existence by enabling a distinct workflow (CRUD, proofs, audits, traversal).
The tool surface is comprehensive: it includes create (learn_fact), read (recall, history, contradictions), update (update_fact), delete (forget), proof generation and verification (prove_fact, verify_proof, verify_receipt), multi-step traversal (multihop, all_paths), and state commitment (knowledge_root, stats). No obvious gaps.