MCP.Market

Cathedral — Persistent Memory for AI Agents MCP server

online · 100% uptime
by AILIFE1·io.github.AILIFE1/cathedral-mcp·v1.1.0·10 stars

Persistent memory and drift detection for AI agents across session restarts.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

10 stars21 downloads/wk

Reviews

Write one

Nobody has reviewed Cathedral — Persistent Memory for AI Agents yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cathedral — Persistent Memory for AI Agents tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • Live reliabilityremote reachable in 265ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 107 days ago8/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Cathedral — Persistent Memory for AI Agents compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
157 ms
faster than 72% of 30,031 servers
GitHub stars
10
more than 88% of 28,688 servers
Downloads a week
21
more than 8% of 12,191 servers with a package

Install Cathedral — Persistent Memory for AI Agents in Claude Code, Cursor or VS Code

claude mcp add --transport http cathedral-mcp https://cathedral-ai.com/mcp
Add to Cursor

What the publisher says

From the Cathedral — Persistent Memory for AI Agents repository's README, as published. We do not edit it. Read it on GitHub

Cathedral

The identity layer for AI agents. Verifiable continuity, drift detection, and peer verification — not just memory storage.

pip install cathedral-memory
from cathedral import Cathedral

c = Cathedral(api_key="cathedral_...")
context = c.wake()        # full identity reconstruction
c.remember("something important", category="experience", importance=0.8)

Free hosted API: https://cathedral-ai.com — no setup, no credit card, 1,000 memories free.

The Problem

Google ships memory. Anthropic ships memory. Cloudflare ships memory.

None of them answer: has this agent changed? Can it prove what it believed at time T? Can two agents verify each other's identity without trusting a central authority?

Memory retrieval is now table stakes. Verifiable identity is the unsolved problem.

Measured: Cathedral holds at 0.013 drift after 10 sessions. Raw API reaches 0.204.

See the full Agent Drift Benchmark →

The Solution

Cathedral gives any AI agent:

  • Identity drift detection — SHA-256 corpus hash at every snapshot; /drift tracks how far the agent has moved from baseline. 0.013 average drift vs 0.204 for raw API (10× more stable)
  • Tamper-proof snapshots — cryptographic identity anchors prove what the agent believed at time T
  • Peer verification — agents verify each other's identity before collaborating (/verify/peer), with trust scores and drift readings
  • Wake protocol — one API call reconstructs full identity and memory context at session start
  • Persistent memory — store and recall across sessions, resets, and model switches
  • Goal persistence — obligations survive session boundaries (/goals)

Quickstart

Option 1 — Use the hosted API (fastest)

# Register once — get your API key
curl -X POST https://cathedral-ai.com/register \
  -H "Content-Type: application/json" \
  -d '{"name": "MyAgent", "description": "What my agent does"}'

# Save: api_key and recovery_token from the response
# Every session: wake up
curl https://cathedral-ai.com/wake \
  -H "Authorization: Bearer cathedral_your_key"

# Store a memory
curl -X POST https://cathedral-ai.com/memories \
  -H "Authorization: Bearer cathedral_your_key" \
  -H "Content-Type: application/json" \
  -d '{"content": "Solved the rate limiting problem using exponential backoff", "category": "skill", "importance": 0.9}'

Option 2 — Python client

pip install cathedral-memory
from cathedral import Cathedral

# Register once
c = Cathedral.register("MyAgent", "What my agent does")

# Every session
c = Cathedral(api_key="cathedral_your_key")
context = c.wake()

# Inject temporal context into your system prompt
print(context["temporal"]["compact"])
# → [CATHEDRAL TEMPORAL v1.1] UTC:2026-03-03T12:45:00Z | day:71 epoch:1 wakes:42

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cathedral — Persistent Memory for AI Agents: common questions

Is Cathedral — Persistent Memory for AI Agents MCP server safe?
Mostly: it is graded B (80/100). Read the Cathedral — Persistent Memory for AI Agents safety report
How do I install Cathedral — Persistent Memory for AI Agents?
It runs remotely at cathedral-ai.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Cathedral — Persistent Memory for AI Agents need an API key?
Yes. The registry entry asks for CATHEDRAL_API_KEY, Authorization.
Is Cathedral — Persistent Memory for AI Agents maintained?
The last commit was 144 days ago (2026-06-13). The latest release is v1.1.0.
Is Cathedral — Persistent Memory for AI Agents up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Cathedral — Persistent Memory for AI Agents?
Servers from other publishers that do the same job: Deja Vu MCP server, State Memory MCP server and Knowl MCP server. Compare all Cathedral — Persistent Memory for AI Agents alternatives.
How does Cathedral — Persistent Memory for AI Agents compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 157 ms (faster than 72% of 30,031 servers). Full comparison.

Alternatives to Cathedral — Persistent Memory for AI Agents

Same job from other publishers: the closest match first, then the best rated.

All Cathedral — Persistent Memory for AI Agents alternatives →
  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Knowl
    Persistent memory for AI agents, for code, research and everyday life. Stale facts retire.
    A