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

Inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail is an MCP integration. Self-correcting agent memory: recall, supersede, revert, forget, GDPR erasure, audit receipts.

Packages and local setup

The published pypi package is inspeximus, version 3.18.0. Its declared MCP transport is stdio.

The package declares 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)..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 3.18.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.