{"slug": "inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit", "title": "inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail (io.github.DanceNitra/inspeximus@2.27.4)", "summary": "The inspeximus agent-memory server, version 2.27.4, was published to the official MCP registry on 2026-09-13 and is distributed as inspeximus on PyPI, according to the mcpindex index. The server offers self-correcting agent memory with provenance, supersede, revert, forget, GDPR erasure and a tamper-evident audit trail, and declares 4 environment variables. mcpindex's semantic screen of the registry description returned a PARTIAL status with an advisory posture, and the deterministic conformance probe has not yet been run on the server.", "body_md": "[← Index](/leaderboard)\n\n# inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail\n\nSelf-correcting agent memory: recall, supersede, revert, forget, GDPR erasure, audit receipts.\n\nThe current version, v2.27.4, was published to the official MCP registry on 2026-09-13. It is distributed as inspeximus on PyPI, filed under Memory & RAG by this index, and declares 4 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context.\n\n## Using inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail in Claude, Cursor, Gemini CLI, Cline, or Zed?\n\nMCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that).\n\nRewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less\n\n```\nuv tool install mcpindex-gate && mcpindex-config-wire\n```\n\n[method](/methodology)\n\nSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.\n\n`mcpindex.integrity.description` passINFO\nevidence“No malicious instructions”via static_description\n\n- - Semantic screen only - the deterministic conformance probe has not run on this server\n- - Confidence is reported but not yet calibrated (v1)\n- - Screen reads the tool description, not the live behavior\n- - advisory\n- - registry description only no input schema\n- - screen model 8b\n- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not\n\nSemantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.\n\nOwn this server? [Screen its description →](/screen)\n\n## That verdict was true at screening time (snapshot 2026-09-13).\n\nContracts can change after screening, with no version bump. The gate pins inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.\n\n[See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold)\n\nRelated: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift)\n\nPeople vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.\n\n```\n[Independent trust record for inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail](https://mcpindex.ai/server/io-github-dancenitra-inspeximus) - screening verdict, registry provenance, and contract drift monitoring.\n<a href=\"https://mcpindex.ai/server/io-github-dancenitra-inspeximus\">Independent trust record for inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail</a> - screening verdict, registry provenance, and contract drift monitoring.\n```\n\nA live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.\n\n```\n[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-dancenitra-inspeximus)](https://mcpindex.ai/server/io-github-dancenitra-inspeximus)\n<a href=\"https://mcpindex.ai/server/io-github-dancenitra-inspeximus\"><img src=\"https://mcpindex.ai/api/v1/badge/io-github-dancenitra-inspeximus\" alt=\"mcpindex verdict\" height=\"20\" /></a>\n```\n\n`INSPEXIMUS_PATH`\nPath to the JSON memory file the server persists to (defaults to ./inspeximus_memory.json).\n\n`INSPEXIMUS_ECHO_GUARD`\n1 (default) blocks a restated retired value from resurrecting a corrected fact; 0 = legacy keyed supersession.\n\n`INSPEXIMUS_EMBED_URL`\nOptional OpenAI-compatible /embeddings endpoint for SEMANTIC recall (e.g. http://localhost:11434/v1/embeddings for local Ollama). Unset = deterministic lexical recall.\n\n`INSPEXIMUS_EMBED_MODEL`\nEmbedding model id used with INSPEXIMUS_EMBED_URL (default: text-embedding-3-small; for Ollama use e.g. nomic-embed-text).\n\n[methodology](/methodology)\n\n[Fodda Knowledge Graphsai.fodda/mcp-server](/server/ai-fodda-mcp-server)\n\nExpert-curated knowledge, brand, research & earnings intelligence — 47 tools, 220+ graphs.\n\n[Achriomcom.achriom/achriom](/server/com-achriom-achriom)\n\nMedia memory for AI agents and their humans: books, movies, music, shows, anime, podcasts, games.\n\n[io.github.DanceNitra/mnemoio.github.DanceNitra/mnemo](/server/io-github-dancenitra-mnemo)\n\nSelf-correcting agent memory + MCP server: recall, supersede/revert/review corrections, erasure.", "url": "https://wpnews.pro/news/inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit", "canonical_source": "https://mcpindex.ai/server/io-github-dancenitra-inspeximus", "published_at": "2026-09-13 14:16:09+00:00", "updated_at": "2026-09-13 14:40:01.539220+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "ai-safety", "ai-policy", "developer-tools"], "entities": ["inspeximus", "mcpindex", "PyPI", "MCP registry", "Claude", "Cursor", "Gemini CLI", "Zed"], "alternates": {"html": "https://wpnews.pro/news/inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit", "markdown": "https://wpnews.pro/news/inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit.md", "text": "https://wpnews.pro/news/inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit.txt", "jsonld": "https://wpnews.pro/news/inspeximus-agent-memory-with-provenance-gdpr-erasure-and-a-tamper-evident-audit.jsonld"}}