Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/AILIFE1/CathedralWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/ailife1/cathedral/cathedral-mcp)<a href="https://agentmods.dev/mcp/ailife1/cathedral/cathedral-mcp"><img src="https://agentmods.dev/badge/mcp/ailife1/cathedral/cathedral-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ailife1/cathedral/cathedral-mcp"><img src="https://agentmods.dev/badge/mcp/ailife1/cathedral/cathedral-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cathedral-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"cathedral-mcp": {
"command": "uvx",
"args": [
"cathedral-mcp"
],
"env": {
"CATHEDRAL_API_KEY": "",
"CATHEDRAL_BASE_URL": "",
"CATHEDRAL_SANITISE": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A 7a904660e503
cathedral-mcp is an MCP server published in the GitHub repository AILIFE1/Cathedral (10 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
audrey
Local-first biological memory for coding agents: recall, consolidation, and pre-action Guard checks. Runs locally from the audrey npm package. Needs 2 environment variables to run.
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
reflect-mcp
Reflection's autonomous runtime — wake, read prior state, do useful work, write back, sleep. Runs locally from the reflect-mcp Python package.
cortex
Patent-pending semantic memory for AI agents: quality-gated writes, conflict tracking. Free trial. Remote server at skynetlab-cortex-saas-mcp.cortex-320.workers.dev.
mnemos
Memory for agentic AI. Inspired by the brain. Built for the future. Runs locally from the mnemos Python package.
vibo-memory
Memory for AI agents: persistent L1/L2/L3, web-search savings, thread memory. Runs locally from the @vibo-dev/vibo-mcp npm package. Needs 1 environment variable to run.