mcpbeat Sign in

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

local only

inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail runs on your own machine — the client starts it, so there is no endpoint to ping. 4 176 installs a week from pypi. Last commit 15 Sep 2026.

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

Installs per day peak 2 968 · avg 848 · +36% w/w
a month agotoday
4 176
Installs / week
pypi · inspeximus
6
Stars
1 open issues
15 Sep 2026
Last commit
0 releases in 90 days
MIT
License
Python

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

A tool parameter reaches a dangerous call

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

A tool parameter reaches a dangerous call erasure_residue.root → tools/release_notes.py:243, erasure_residue.root → tools/release_notes.py:250
            proc = subprocess.run([sys.executable, "-c", code], cwd=tmp, capture_output=True,
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    m = Inspeximus(path=os.path.join(d, name))
                for k, n in eval(kinds):  # noqa: S307 - our own repr of a sorted list of pairs
Builds a database query by concatenation ai-act.html:348
                <td><span class="mk no">delete + legal-hold, not verifiable</span></td>

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

A tool parameter here reaches a dangerous call

That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add inspeximus -- uvx inspeximus
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "inspeximus": {
      "args": [
        "inspeximus"
      ],
      "command": "uvx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.inspeximus]
command = "uvx"
args = ["inspeximus"]
.cursor/mcp.json
{
  "mcpServers": {
    "inspeximus": {
      "args": [
        "inspeximus"
      ],
      "command": "uvx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "inspeximus": {
      "args": [
        "inspeximus"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: INSPEXIMUS_PATH (Path to the JSON memory file the server persists to (defaults to ./inspeximus_memory.json).), INSPEXIMUS_ECHO_GUARD (1 (default) blocks a restated retired value from resurrecting a corrected fact; 0 = legacy keyed supersession.), INSPEXIMUS_EMBED_URL (Optional OpenAI-compatible /embeddings endpoint for SEMANTIC recall (e.g. http://localhost:11434/v1/embeddings for local Ollama). Unset = deterministic lexical recall.), INSPEXIMUS_EMBED_MODEL (Embedding model id used with INSPEXIMUS_EMBED_URL (default: text-embedding-3-small; for Ollama use e.g. nomic-embed-text).). The author declared them in the registry entry; get the values from the project itself.

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

same job, measured the same way
Mnemo
by dancenitra

Self-correcting agent memory + MCP server: recall, supersede/revert/review corrections, erasure.

951 installs/wk local only
Nahuali
by arakiss

Trust-aware agent memory with evidence-backed recall, self-inspection, and audit history.

local only
Lians Agent Memory
by ebeirne

Bitemporal memory for AI agents with point-in-time recall and tamper-evident audit history.

172 installs/wk local only
Agent Memory MCP
by kira-autonoma

Agent memory MCP server with provenance tracking, decay-weighted recall, and feedback loops.

32 installs/wk local only
Attestari
by attestari

Auditable memory for AI agents: provable deletion, tamper-evident audit, time-travel recall.

146 installs/wk local only
EU Audit Trail
by jellewas

Tamper-evident audit trail MCP server for EU AI Act & GDPR compliance.

72 installs/wk local only
Tradememory Protocol
by mnemox-ai

Tamper-evident decision audit trail and outcome-weighted memory for AI trading agents.

119 installs/wk local only
Agent Receipts MCP
by dhanushs1912-svg

EU AI Act-ready audit trail: signed, tamper-evident receipts proving what your AI agents did.

46 installs/wk local only

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

Answers built from our own checks of this server.

Why is there no uptime for 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 runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the pypi package inspeximus was installed 4 176 times last week.
How do I connect inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls inspeximus straight from pypi; nothing to host, nothing to sign up for.
How many people use inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail?
The pypi package inspeximus was installed 4 176 times in the last week. Week over week that is +36%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail open source?
Yes — it is published under the MIT licence, written in Python, 6 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.