Integration — MCP Server

Validated memory for your LLM stack

32 MCP tools. Bi-temporal queries. Quarantine with human oversight. Every write validated by 18 tests and sealed (SHA-512).

Model Context Protocol · Swiss-hosted · Claude Desktop, Cursor, VS Code

Start free Technical docs

Free plan · no credit card · Swiss hosting

01 — Capabilities

What makes AxiomSeal different

Validation, sealing, and audit primitives — exposed through one standardized MCP interface.

Quarantine + Human Oversight

Writes that fail validation are quarantined, not stored silently. Review, release or reject them — every decision stays in the audit trail.

eon_list_governanceeon_resolve_governanceeon_governance_stats

Bi-Temporal Queries

Time-travel queries: what did the system believe on 2024-03-15? Built for the traceability Art. 12 expects — binding for high-risk systems from 2 December 2027.

eon_as_ofeon_invalidate

Sealed Integrity

SHA-512 sigma hash per memory, chained. Silent edits break the chain — and get caught.

eon_verify_integrity

Explainable Validation

18 tests per write, then a 4-stage verdict: ACCEPT / REQUIRE_CONFIRM / QUARANTINE / REJECT — each with a stated reason.

eon_createeon_list_governance

Memory Lineage

Which memory superseded which, and when? The supersedes chain is stored bi-temporally and exportable.

eon_memory_lineageeon_invalidate

Core Memory + Sessions + Goals

Search, create, projects, sessions, goals, health, stats — the full working set.

eon_searcheon_create+20 more

02 — Comparison

vs. other memory solutions

Feature by feature, against public documentation (June 2026). Where a competitor ships something we do not, the table says so.

Scroll table sideways

Feature	Mem0	Zep	Supermemory	Letta	AxiomSeal
Validation tests at write-time (18)	No	No	No	No	Yes
SHA-512 sealed chain	No	No	No	No	Yes
Quality tiers + quarantine	No	No	No	No	Yes
Fact invalidation + provenance	No	Yes	No	No	Yes
SOC 2 / HIPAA certification	Yes	Not stated in public documentation	Not stated in public documentation	Not stated in public documentation	No
Swiss hosting (CH data residency)	No	No	No	No	Yes

Based on public documentation, June 2026. Zep ships fact invalidation and provenance; Mem0 is SOC 2 + HIPAA certified. Corrections: info@ai-developer.ch

Full market comparison on the compare page.

03 — Install

Connect in one command

1. One command

No API key needed. Your browser opens, you log in, and you are connected. Nothing is written into your project folder.

Terminal

Works in Claude Code. Restart your client afterwards.

claude mcp add --transport http axiomseal https://mcp.axiomseal.com/mcp/

Working across several projects? Add --scope user and it is set up once for your whole account:

Terminal (all projects)

claude mcp add --scope user --transport http axiomseal https://mcp.axiomseal.com/mcp/

2. Or let your AI do it

Paste this into Claude, Cursor, Gemini or any assistant that can run commands. It ends by verifying the connection, so you get told the truth about whether it worked.

Prompt

Copy into your assistant.

Please connect me to AxiomSeal, a memory system that speaks MCP.

Preferred way (Claude Code, no API key needed — a browser window opens and I log in):
  claude mcp add --transport http axiomseal https://mcp.axiomseal.com/mcp/

If my client cannot do OAuth (Gemini CLI, older bridges), use this instead and
put it in my client's own MCP config — never in a file inside a git repository:
{
  "mcpServers": {
    "axiomseal": {
      "type": "streamable-http",
      "url": "https://mcp.axiomseal.com/mcp/",
      "headers": {
        "Authorization": "Bearer eon_YOUR_API_KEY"
      }
    }
  }
}

The MCP connection alone does NOT install the automatic hooks (memory search
on every prompt, session save). To add them, fetch the hook files with my
API key and follow the registration instructions in the response:
  GET https://app.axiomseal.com/api/proxy/cli/hooks   (X-API-Key header)
After installing, run:  python ~/.claude/hooks/selftest.py
and show me its output.

If you add anything to my CLAUDE.md, wrap it exactly like this so it can be
removed cleanly later:
  <!-- AXIOMSEAL:BEGIN -->
  ...content...
  <!-- AXIOMSEAL:END -->

When you are done, run the eon_health tool and show me its output. Do not tell
me it worked until you have seen that output. If anything failed, say which step.

3. Manual setup, for clients without OAuth ▸

Gemini CLI and some local bridges cannot do the browser login and need a key. Paste this into that client’s own MCP settings.

MCP config

Replace eon_YOUR_API_KEY with the key from your dashboard.

{
  "mcpServers": {
    "axiomseal": {
      "type": "streamable-http",
      "url": "https://mcp.axiomseal.com/mcp/",
      "headers": {
        "Authorization": "Bearer eon_YOUR_API_KEY"
      }
    }
  }
}

Do not commit this into a git repository. A key that has been committed stays in the history even after you delete the file — rotate it in Settings if that happens. The command in step 1 avoids this entirely, because nothing is stored in the project.

04 — Compliance

Swiss-hosted. Built for EU AI Act traceability.

Data Residency

All data stored in St. Gallen, Switzerland. No transit outside CH/EU.

EU AI Act Article 12

Automatic record-keeping: every write stores its validation verdict, retrievable via eon_list_governance, plus audit-log export — built for the traceability Art. 12 expects, binding for high-risk systems from 2 December 2027.

EU AI Act Article 50

Validation verdicts and provenance are exportable, supporting transparency and disclosure workflows.

GDPR / Swiss DSG

Right to export, right to be forgotten, DPA available on request.

05 — Get started

Give your LLMs memory you can audit

Free plan. No credit card. Cancel anytime.

See pricing Read the docs