All MCP Servers
AI & MemoryMCP RegistrypypiB · 77

inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail MCP server

io.github.DanceNitra · Updated

Self-correcting agent memory: recall, supersede, revert, forget, GDPR erasure, audit receipts.

At a glance

inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail is an MCP server in the AI & Memory category. It runs locally over stdio via `uvx inspeximus`, and declares no required credentials. It scores B (77/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 8GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add inspeximus -- uvx inspeximus
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What does inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail need from you?

Configuration only — Declares config values but no credentials.

  • INSPEXIMUS_PATHoptionalEnvironment variable

    Path to the JSON memory file the server persists to (defaults to ./inspeximus_memory.json).

  • INSPEXIMUS_ECHO_GUARDoptionalEnvironment variable

    1 (default) blocks a restated retired value from resurrecting a corrected fact; 0 = legacy keyed supersession.

  • INSPEXIMUS_EMBED_URLoptionalEnvironment variable

    Optional OpenAI-compatible /embeddings endpoint for SEMANTIC recall (e.g. http://localhost:11434/v1/embeddings for local Ollama). Unset = deterministic lexical recall.

  • INSPEXIMUS_EMBED_MODELoptionalEnvironment variable

    Embedding model id used with INSPEXIMUS_EMBED_URL (default: text-embedding-3-small; for Ollama use e.g. nomic-embed-text).

Pass secrets through your shell environment rather than committing them into a config file.

What tools does inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Source analysis currently covers npm packages only. This server ships as a Python package, which needs a different parser.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit today — Actively maintained.
  • 8 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 77

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 0 days ago.

  • Adoption20%29%

    8 stars.

  • Transparency20%75%

    3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%100%

    Publishes a pinned version (3.26.0).

Documentation

Full README

inspeximus

Tamper-evident long-term memory for AI agents. Correct a fact once and the old value stays retired; erase a person and prove it; show an auditor what the agent knew when it acted. One zero-dependency Python file, plus an MCP server.

The erasure proof covers this store only, not a vector index, prompt logs, or backups, and it is an integrity primitive, not a compliance certification.

Quickstart · Docs · vs mem0 and Graphiti · Migrate from mem0 · EU AI Act and GDPR evidence · Claude Code, one line · Transparency log · PyPI

bash
pip install "inspeximus[crypto]"
inspeximus demo          # a first result: offline, touches nothing of yours
python
from inspeximus import Inspeximus

m = Inspeximus("memory.json")
m.remember("The staging database is db-3.internal", key="staging-db")
m.remember("The staging database is db-7.internal", key="staging-db")   # a correction
m.recall("which staging database")[0]["text"]   # 'The staging database is db-7.internal'
m.revert("staging-db")                            # and it is reversible, on purpose

memory.json is a name, not a format: a new store is a SQLite file. Read it through inspeximus or the sqlite3 module, never with json.load or cat.

| | What you get | |---|---| | A correction that holds | remember(key=...) retires the old value by key. Restating the stale text does not bring it back; revert() does, as a recorded decision. | | Erasure you can prove | forget_subject() removes every record about a person, leaves a signed content-free tombstone, and erasure_certificate() lets a third party check it with no private key. For authorship, the third party pins your public key (expected_pubkey) and witnesses the anchor. It covers this store only. | | What the agent knew when it acted | A signed, hash-chained action ledger; matches() binds a retained transcript to its entry. | | When it happened | RFC 3161 timestamps, and a check whether the authority was on the EU trusted list on that date. | | Evidence an auditor can read | inspeximus compliance labels the evidence by article; export as a draft-sharif-agent-audit-trail-04 file. | | Any agent, one line | MCP server for Claude Code, Cursor, Windsurf, Codex and Cline; adapters for LangChain, LangGraph, ADK and more. |


Why inspeximus

Use it when the agent runs for days and the facts it holds will change under it, and when somebody can later ask what it knew and what it erased. That is the whole design brief.

| You have | Reach for | |---|---| | An agent that keeps confidently repeating a value you already corrected | remember(key=...): the correction wins, the restatement does not bring the old value back, revert() is a recorded decision | | A right-to-erasure request, or an auditor asking what the agent knew when it acted | forget_subject() with erasure_certificate(); the signed action ledger with matches() | | Claude Code, Cursor, Windsurf, Codex or Cline, and no memory between sessions | the MCP server, one config line | | A framework (LangChain, LangGraph, ADK, Hermes, Haystack) and no way to prove a memory write happened | the adapters and the receipt chain |

agno is the one that is not ours. It ships an official integration example in its own cookbook, `cookbook/11_memory/integrations/inspeximus_integration.py`, merged in agno#10146 on 2026-09-20, alongside mem0, zep, memori and dakera. Their own README describes it as *"inspeximus for corrections that stay corrected."* We did not write that file's home and we do not maintain it, which is exactly why it is worth listing: it is one integration a reader can check without taking our word for anything. The same holds for agmi, an agent-memory integrity scorecard whose maintainer merged our three-row adapter, `agmi/adapters/inspeximus_rows.py`, in agmi#1 after reproducing it himself.

Not the right tool when you want a hosted service with a dashboard, a knowledge graph over documents, or the highest score on a conversational-recall benchmark. mem0, Zep and cognee lead there, and the comparison page says where each of us wins and where we do not.

Excerpt — the full document is on GitHub.

Maintain inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-dancenitra-inspeximus)](https://mcp-skills-hub.vercel.app/mcps/io-github-dancenitra-inspeximus)

Catalog data refreshed . Something wrong? Report it.