
AxiomSeal
Free plan · From ≈ $35/moActively maintained
not read yet
Use
- For
- developers and teams using Claude Code, Cursor or MCP clients who need checked, persistent AI memory
- Price
- Free plan · From ≈ $35/moCHF 29 · pricing page, read Oct 24, 2026
- Activity
- Actively maintainedsite updated 2 weeks ago
- Used for
- check AI memories for contradictions before storing them
- keep a tamper-evident record of what an assistant learned
- produce signed audit reports for EU AI Act traceability
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsaxiomseal.com ↗
- Domain since2026domain registered
- HeadquartersSt. Gallen, CHper their site
- Trains on your dataNoprivacy policy ↗
- Certifications they stateGDPR · PCI DSSsecurity page ↗
- Data processing agreementpublishedDPA ↗
- Privacy policy updated2026-07-04privacy policy ↗
- Security contactsecurity.txt
“Your content is processed only to deliver the service, never for advertising and never to train models.”
privacy policy ↗
These are AxiomSeal's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP servercom.axiomseal/axiomsealverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-24
- Address to connectmcp.axiomseal.com/mcp
- MCP docsaxiomseal.com/mcpthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Figure and bar: visits/mo, estimate · year: online since
- #1

AxioRankMCP · open
Checks every AI agent tool call against policy, scans payloads for leaked secrets and destructive SQL, and writes a signed audit trail.
20MaintainedFrom $49/mo - #2

KorelyMCP · sign-in
Stores agent memories as typed facts with validity dates, resolving contradictions and serving current or past-date truth via API.
9ActiveFrom ≈ $21/mo2025 - #3

CalendarMCPMCP · sign-in
Gives AI agents an HTTP endpoint to read, create, move and check free time across Google Calendar events.
4ActiveFree - #4

AIMEATMCP · sign-in
Gives AI assistants a persistent memory and a shared layer of actions, reachable through an MCP server and a web portal.
2Active - #5

DijinMCP · sign-in
Keeps one user-owned memory that Claude, ChatGPT and Cursor recall, citing the source of each answer.
1MaintainedFrom $8.33/mo2025 - #6

LeapMemoryMCP · sign-in
Stores exact facts a user tells an AI assistant and recalls them in later chats, served to any model over MCP.
1ActiveFrom $20/mo
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use AxiomSeal for?
Sign in to leave a noteWhat is AxiomSeal?
Stores AI assistant memories after running 19 validation tests and sealing each in a tamper-evident SHA-512 hash chain. It is listed in the Atlas under Agents.
Who is AxiomSeal for?
developers and teams using Claude Code, Cursor or MCP clients who need checked, persistent AI memory
How much does AxiomSeal cost?
AxiomSeal has a free plan; paid plans start at ≈ $35/mo (CHF 29/mo), per its pricing page on 2026-10-24.
Is AxiomSeal free?
Yes, AxiomSeal has a free plan, per its pricing page on 2026-10-24.
Do people use AxiomSeal?
Little sign of use.
Is AxiomSeal still maintained?
Actively maintained: site updated 2 weeks ago.
Does AxiomSeal train AI on your data?
No, per its privacy policy (2026-10-24): “Your content is processed only to deliver the service, never for advertising and never to train models.”
Is AxiomSeal safe?
We do not audit vendors. What AxiomSeal publishes, read 2026-10-24: GDPR, PCI DSS stated on its security page; on training with your data, “Your content is processed only to deliver the service, never for advertising and never to train models.”.
What are alternatives to AxiomSeal?
In Agents, by use: AxioRank, Korely, CalendarMCP, AIMEAT, Dijin, LeapMemory.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.