verifiable-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VMEM_STATE | No | Path to the state file for verifiable memory (default: ~/.verifiable_memory) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| learn_factA | Store a fact (subject, relation, object) the agent must recall EXACTLY later, with its source. Call whenever the user states a fact, preference, decision, name, number, or rule worth remembering — it persists across sessions and is never silently distorted. Optional valid_from for valid-time. |
| recallA | Look up a stored fact and return the answer WITH its cited source — or an honest 'unknown'. ALWAYS call this before answering a factual or memory question instead of guessing: it returns nothing rather than hallucinating, and includes a signed, verifiable receipt. Optional as_of for valid-time. |
| update_factA | Update a fact's value without retraining: closes live versions (valid_to=t) and opens a new one. History is preserved. |
| historyB | Full life-line of a fact (all versions live+closed, with sources and valid-time). Audit/compliance. |
| forgetA | Permanently and PROVABLY delete a stored fact (GDPR / right-to-be-forgotten). Use when the user asks to forget or remove information — the fact is fully erased and you get a signed proof of deletion. object optional (omit to delete all values). |
| contradictionsA | Audit knowledge for conflicts: for functional relations (one value expected, e.g. 'capital','birthdate') return any (subject,relation) holding >1 live value, showing BOTH sources — call before trusting facts that may have been updated or come from multiple sources. |
| knowledge_rootA | Merkle root committing the entire current knowledge state (one hash). |
| prove_factA | Merkle inclusion proof that a fact is in the knowledge state (without revealing other facts). |
| verify_proofC | Verify a Merkle inclusion proof (leaf, proof, root). |
| verify_receiptA | Verify a signed receipt returned by recall/forget (tamper-evident). |
| multihopC | Multi-hop chain: start entity + list of relations, follows subject->object each step (exact only, 0% hallucination). |
| all_pathsC | All exact fact-paths between start and end entities (each path citable). |
| statsC | Counts + current knowledge root. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mars-proj/verifiable-memory'
If you have feedback or need assistance with the MCP directory API, please join our Discord server