inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
Agent memory where corrections stick, with provable GDPR erasure and a signed audit trail
- Platforms
- CLI, self-hosted
- Runs
- Locally
- Version
- 3.27.0
- Listing updated
- 5 days ago
Similar MCP servers
About inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail is an MCP server for knowledge and memory. It runs locally on your machine and is started by your AI client.
Inspeximus is a long-term memory store for agents built on one rule: when you correct a fact under a key, the old value stays retired. Restating the stale text does not bring it back; an explicit revert does, as a recorded decision. Correction is by key with no language model involved.
Beyond recall, it can erase everything about a person and leave a signed, content-free tombstone with a certificate a third party can check. A hash-chained action ledger records what the agent knew when it acted, and RFC 3161 timestamps back the dates. The author is clear that erasure proof covers this store only, not vector indexes, prompt logs or backups, and that it is an integrity tool, not a compliance certification.
It ships as a zero-dependency Python file plus a stdio MCP server for Claude Code, Cursor, Windsurf, Codex and Cline, with adapters for LangChain and others. Memory saves to a local file, and semantic recall is optional through an OpenAI-compatible embeddings endpoint such as local Ollama.
Install
Run in a terminal
claude mcp add inspeximus -- uvx inspeximusAdd to claude_desktop_config.json
{
"mcpServers": {
"inspeximus": {
"command": "uvx",
"args": [
"inspeximus"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"inspeximus": {
"command": "uvx",
"args": [
"inspeximus"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"inspeximus": {
"type": "stdio",
"command": "uvx",
"args": [
"inspeximus"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"inspeximus": {
"command": "uvx",
"args": [
"inspeximus"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"inspeximus": {
"command": "uvx",
"args": [
"inspeximus"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
INSPEXIMUS_PATHPath to the JSON memory file the server persists to (defaults to ./inspeximus_memory.json).INSPEXIMUS_ECHO_GUARD1 (default) blocks a restated retired value from resurrecting a corrected fact; 0 = legacy keyed supersession.INSPEXIMUS_EMBED_URLOptional OpenAI-compatible /embeddings endpoint for SEMANTIC recall (e.g. http://localhost:11434/v1/embeddings for local Ollama). Unset = deterministic lexical recall.INSPEXIMUS_EMBED_MODELEmbedding model id used with INSPEXIMUS_EMBED_URL (default: text-embedding-3-small; for Ollama use e.g. nomic-embed-text).
What it does
- Corrections that hold
- A keyed update retires the old value, and restating it does not revive it.
- Reversible
- Revert restores a retired value as a recorded decision.
- Provable erasure
- Removes a subject's records and issues a verifiable certificate.
- Action ledger
- Signed, hash-chained record of what the agent knew.
- Optional semantic recall
- Plug in a local or hosted embeddings endpoint.
- Local file storage
- Memory persists to a path you choose.
Good for
- Keep an agent from reverting to an outdated config value
- Erase a user's data and hand over proof
- Show an auditor what an agent knew at decision time
- Run a private agent memory offline
- Migrate from another agent memory library
Pricing
Pricing unknown
Installed free from PyPI; licence not published
Prices change. Check pypi.org before you buy.
inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail FAQ
Does erasure cover backups?
No. The proof covers this store only, not vector indexes, prompt logs or backups.
Is it a compliance certification?
No, the author calls it an integrity primitive.
Is an LLM involved in corrections?
No, correction is by key with no model in the loop.
How does it persist?
To a file set by INSPEXIMUS_PATH, defaulting to ./inspeximus_memory.json.
How do I add inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail to Claude Code?
Run this command in your terminal: claude mcp add inspeximus -- uvx inspeximus
What are the best alternatives to inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail?
The closest alternatives to inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail are Heartwood Memory — governed memory for AI agents, Memory Pulse, Saihm MCP Server Pro, persistent-memory and SuperLocalMemory.
Where this comes from
- Description: written from the project's README and the project's website.
- Install steps: from the official MCP Registry entry.