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/nworks3d/THOR-memory-bible-for-AIWrote 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/nworks3d/thor-memory-bible-for-ai/thor)<a href="https://agentmods.dev/mcp/nworks3d/thor-memory-bible-for-ai/thor"><img src="https://agentmods.dev/badge/mcp/nworks3d/thor-memory-bible-for-ai/thor/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/nworks3d/thor-memory-bible-for-ai/thor"><img src="https://agentmods.dev/badge/mcp/nworks3d/thor-memory-bible-for-ai/thor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
thor 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 Changed e6696f02a981
- 1mo ago First seen · 12 lines scan A e188897e2fc0
thor is an MCP server published in the GitHub repository nworks3d/THOR-memory-bible-for-AI (5 stars, last pushed 1mo ago), licensed GPL-3.0. 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
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.
xmemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST. Runs locally from the @xmemo/client npm package. Needs 2 environment variables to run.
perenna
A lightweight, Git-backed permanent memory for AI agents. Runs locally from the perenna Python package. Needs 4 environment variables to run.
dakera-mcp
MCP server "dakera-mcp" as configured in Dakera-AI/dakera-mcp. Runs in Docker (ghcr.io/dakera-ai/dakera-mcp:0.9.8).
atomicmemory
MCP server "atomicmemory" as configured in atomicstrata/atomicmemory. Runs locally from the atomicmemory-mcp npm package. Needs 7 environment variables to run.