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

What the code does

We read the source, 4 d ago · rules 995398eba69f

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.

            proc = subprocess.run([sys.executable, "-c", code], cwd=tmp, capture_output=True,

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    env = dict(os.environ, GOV_FALSIFY="1")

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))

    return subprocess.run(["git", *args], cwd=cwd, capture_output=True, text=True)

                for k, n in eval(kinds):  # noqa: S307 - our own repr of a sorted list of pairs

                <td><span class="mk no">delete + legal-hold, not verifiable</span></td>

    hp = run(hook_cmd, cwd=launch, shell=True, extra_env=cc_env,

    env = dict(os.environ, INSPEXIMUS_STORE_FORMAT=fmt)

KEYISH = re.compile(r"(\.key$|\.pem$|id_ed25519$|id_rsa$|secret|private)", re.I)

        with urllib.request.urlopen("https://api.telegram.org/bot%s/sendMessage" % vals["NOTIFY_BOT_TOKEN"],

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

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.

claude mcp add inspeximus -- uvx inspeximus

{
  "mcpServers": {
    "inspeximus": {
      "command": "uvx",
      "args": [
        "inspeximus"
      ]
    }
  }
}

[mcp_servers.inspeximus]
command = "uvx"
args = ["inspeximus"]

{
  "mcpServers": {
    "inspeximus": {
      "command": "uvx",
      "args": [
        "inspeximus"
      ]
    }
  }
}

{
  "servers": {
    "inspeximus": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "inspeximus"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: 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)).