inspeximus — Claude Code MCP server: what it does and install
Persistent memory for AI agents with verifiable audit trails and permanent corrections. Keeps stale data retired and generates proof for GDPR deletions.
claude mcp add --env INSPEXIMUS_PATH=<INSPEXIMUS_PATH> --env INSPEXIMUS_ECHO_GUARD=<INSPEXIMUS_ECHO_GUARD> --env INSPEXIMUS_EMBED_URL=<INSPEXIMUS_EMBED_URL> --env INSPEXIMUS_EMBED_MODEL=<INSPEXIMUS_EMBED_MODEL> --transport stdio inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit -- uvx inspeximusWhat inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail does
The server saves agent knowledge directly into a local SQLite database. When a value is updated with remember under a key, the earlier version is retired permanently. Repeating outdated phrasing will not revive it. If a change needs undoing, revert logs that rollback as a deliberate decision.
Agent activities feed into a hash-linked ledger marked with RFC 3161 timestamps. The core engine fits in a single Python file with no dependencies. Cryptographic checks need the optional inspeximus[crypto] package.
GDPR erasure proofs apply strictly to this SQLite database file. External vector databases, prompt logs and server backups remain untouched, so those systems require separate handling.
What it helps with
- retire superseded facts without risk of agent regression
- produce verifiable cryptographic certificates for GDPR erasure requests
- track agent decisions in a hash-chained action ledger with RFC 3161 timestamps
- export compliance evidence matching draft-sharif-agent-audit-trail-04 specifications
Example prompts for the agent
- Store the updated staging database address under the staging-db key
- Purge all records for this user and generate the erasure certificate
- Show the action ledger entries along with their RFC 3161 timestamp
How to install inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
Platform CLI
claude mcp add --env INSPEXIMUS_PATH=<INSPEXIMUS_PATH> --env INSPEXIMUS_ECHO_GUARD=<INSPEXIMUS_ECHO_GUARD> --env INSPEXIMUS_EMBED_URL=<INSPEXIMUS_EMBED_URL> --env INSPEXIMUS_EMBED_MODEL=<INSPEXIMUS_EMBED_MODEL> --transport stdio inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit -- uvx inspeximusReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from inspeximus <command>
Platform CLI
codex mcp add inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit --env INSPEXIMUS_PATH=<INSPEXIMUS_PATH> --env INSPEXIMUS_ECHO_GUARD=<INSPEXIMUS_ECHO_GUARD> --env INSPEXIMUS_EMBED_URL=<INSPEXIMUS_EMBED_URL> --env INSPEXIMUS_EMBED_MODEL=<INSPEXIMUS_EMBED_MODEL> -- uvx inspeximusReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from inspeximus <command>
Config file
{
"mcpServers": {
"inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit": {
"command": "uvx",
"args": [
"inspeximus"
],
"env": {
"INSPEXIMUS_PATH": "<INSPEXIMUS_PATH>",
"INSPEXIMUS_ECHO_GUARD": "<INSPEXIMUS_ECHO_GUARD>",
"INSPEXIMUS_EMBED_URL": "<INSPEXIMUS_EMBED_URL>",
"INSPEXIMUS_EMBED_MODEL": "<INSPEXIMUS_EMBED_MODEL>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from inspeximus <command>
Config file
{
"servers": {
"inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit": {
"type": "stdio",
"command": "uvx",
"args": [
"inspeximus"
],
"env": {
"INSPEXIMUS_PATH": "<INSPEXIMUS_PATH>",
"INSPEXIMUS_ECHO_GUARD": "<INSPEXIMUS_ECHO_GUARD>",
"INSPEXIMUS_EMBED_URL": "<INSPEXIMUS_EMBED_URL>",
"INSPEXIMUS_EMBED_MODEL": "<INSPEXIMUS_EMBED_MODEL>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from inspeximus <command>
Platform CLI
gemini mcp add -e INSPEXIMUS_PATH=<INSPEXIMUS_PATH> -e INSPEXIMUS_ECHO_GUARD=<INSPEXIMUS_ECHO_GUARD> -e INSPEXIMUS_EMBED_URL=<INSPEXIMUS_EMBED_URL> -e INSPEXIMUS_EMBED_MODEL=<INSPEXIMUS_EMBED_MODEL> inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit uvx inspeximusReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from inspeximus <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
How to install inspeximus in Claude Code?
Run the command claude mcp add inspeximus -- uvx inspeximus in your terminal to configure the tool via uvx.
What storage format does inspeximus use?
It writes directly to a SQLite database, even when the target filename carries a .json extension. Inspect it with sqlite3 or the library methods rather than standard JSON parsers.
Does the GDPR certificate cover prompt logs?
No, the proof covers the local SQLite store only. Vector databases, prompt histories and backups must be cleared through their own separate processes.
