MCP.Market

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

by DanceNitra·io.github.DanceNitra/inspeximus·v3.26.0·7 stars
No reviews yet

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

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

not scanned yet

Adoption
Established

7 stars4.8k downloads/wk

Reviews

Write one

Nobody has reviewed inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

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

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

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

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 4,460 AI and agents servers
GitHub stars
7
more than 81% of 2,711 AI and agents servers
Downloads a week
4,782
more than 95% of 1,538 AI and agents servers with a package

Release history: 40 versions in the registry since 2026-09-17, latest 2026-10-29, typically several a day.

Install inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail in Claude Code, Cursor or VS Code

claude mcp add inspeximus -- uvx inspeximus
Add to Cursor

What the publisher says

From the inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail repository's README, as published. We do not edit it. Read it on GitHub

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.

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

pip install inspeximus
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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

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

Is inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail safety report
How do I install inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail maintained?
The last commit was 33 days ago (2026-10-02). The latest release is v3.26.0.
What can I use instead of inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail?
Servers from other publishers that do the same job: Agent Recall MCP server, three.ws Provenance MCP server and Total Agent Memory MCP server. Compare all inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail alternatives.
How does inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail compare with other AI and agents MCP servers?
safety score 92/100 (higher than 90% of 4,460 AI and agents servers); github stars 7 (more than 81% of 2,711 AI and agents servers); downloads a week 4,782 (more than 95% of 1,538 AI and agents servers with a package). Full comparison.

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

Same job from other publishers: the closest match first, then the best rated.

All inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail alternatives →
  • Agent Recall
    Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
    A
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    More from nirholas →
    B
  • Total Agent Memory
    Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall
    A
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail vs Agent Recallinspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail vs three.ws Provenanceinspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail vs Total Agent Memory