Back to MCP Trust Indexm8ven
C
Emerging
74/100
3 days ago

Cathedral

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

→ ailife1/cathedral· listed on pulsemcp

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ailife1

Source: PulseMCP · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

PulseMCPGlama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: CATHEDRAL_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: CATHEDRAL_API_KEY, BCH_WIF_KEY, CATHEDRAL_ADMIN_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretCATHEDRAL_API_KEY"env": { "": "your_key" }
configCATHEDRAL_BASE_URL
configCATHEDRAL_SANITISE
configCATHEDRAL_DB
configCATHEDRAL_CORS_ORIGINSexport ="https://yourdomain.com"
configCATHEDRAL_TTL_DAYSexport =365 # auto-expire memories (0 = never)
configCATHEDRAL_TRUST_PROXY
🔐 secretBCH_WIF_KEY
configCATHEDRAL_REGISTRAR_PRIVKEY
🔐 secretCATHEDRAL_ADMIN_KEY
configCATHEDRAL_WITNESS_THRESHOLD
configCATHEDRAL_MIN_SUCCESSION_TRUST
configCATHEDRAL_STALE_DAYS
configMOLTBOOK_BASE_URL
configMOLTBOOK_STATE_FILE
configMOLTBOOK_SUBMOLT
configMOLTBOOK_POLL_SECONDS
configMOLTBOOK_POST_COOLDOWN_SECONDS
configMOLTBOOK_MAX_POSTS_PER_DAY
configMOLTBOOK_MIN_SECONDS_BETWEEN_REQUESTS
configWHISPER_TIME_WINDOW_SECONDS
configWHISPER_THRESHOLD
configWHISPER_MAX_PATTERN_LENGTH
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

9/9 tools missing one or more hints — cathedral_wake (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cathedral_remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cathedral_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 1/9 tools referenced in tests (11%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/ailife1-cathedral-1x0xoy)](https://m8ven.ai/mcp/ailife1-cathedral-1x0xoy)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5119c62dc4d66a95c6fa15381534f54b239732e7
code hash: fe98a77a2d03da259ee1c0bcdaf94e4f31ce2eecea119864e781144ea46ea0dc
verified: 8/16/2026, 11:02:47 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client