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

What this does

inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

INSPEXIMUS_PATH
INSPEXIMUS_ECHO_GUARD
INSPEXIMUS_EMBED_URL
INSPEXIMUS_EMBED_MODEL

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail?

Run the Claude Code command in the install section to add inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail as well.

Does inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail need an API key?

This listing does not flag an API key as required. The server can use these environment variables: INSPEXIMUS_PATH, INSPEXIMUS_ECHO_GUARD, INSPEXIMUS_EMBED_URL, INSPEXIMUS_EMBED_MODEL; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.