Axiomseal

com.axiomsealPublished by axiomseal.comOfficial publisherv1.1.0Updated Oct 24, 2026

Truth-validated, SHA-512-sealed AI memory for Claude & Cursor. Free tier, OAuth, 38 tools.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Axiomseal is a remote, OAuth-protected memory service for Claude and Cursor that stores AI memory with truth validation and SHA-512 sealing.

What you can do
Store and recall AI memory through a hosted memory service, described as truth-validated and SHA-512-sealed, for use across Claude and Cursor sessions. The provider lists 38 tools, but no tool names or descriptions are published, so the exact operations cannot be confirmed. A free tier is offered alongside OAuth sign-in.
When to use it
Consider it if you want a hosted, shared memory layer that persists context across Claude and Cursor sessions and you are comfortable with a third-party service holding that memory. Because the tool list is unpublished, evaluate it directly before relying on it.
Requirements
A remote MCP endpoint at mcp.axiomseal.com over streamable HTTP, with OAuth authentication required. No packages, environment variables or headers are declared. A free tier is mentioned; network access is needed.
Before you install
Memory content is sent to a third-party hosted service, so avoid storing secrets or sensitive data. OAuth grants the server access tied to your account. The 38 tools are not documented, so their read, write or delete behavior is unknown. Check what the free tier covers and whether paid plans apply.

Installation

In SourceWeft

  1. Open Axiomseal in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.axiomseal%2Faxiomseal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "axiomseal": {
      "type": "http",
      "url": "https://mcp.axiomseal.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.