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/hsusul/loreInstalling this writes the configuration, not the program: `lorectl` has to be on your PATH already, or the server will not start.
Wrote 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/hsusul/lore/claude-code-lore)<a href="https://agentmods.dev/mcp/hsusul/lore/claude-code-lore"><img src="https://agentmods.dev/badge/mcp/hsusul/lore/claude-code-lore/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/hsusul/lore/claude-code-lore"><img src="https://agentmods.dev/badge/mcp/hsusul/lore/claude-code-lore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lore 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 3d 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
{
"lore": {
"command": "lorectl",
"args": [
"mcp"
],
"env": {
"LORE_AGENT": "claude-code"
}
}
}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.
- 3d ago First seen · 11 lines scan A 36a5af45ad2d
lore is an MCP server published in the GitHub repository hsusul/lore (134 stars, last pushed yesterday), licensed Apache-2.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-11-04.
lore compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| lorehsusul/lore | MCP server | 134 | yesterday | Apache-2.0 | A | — | Claude Code |
| hypermnesia-mcpcdeust/Cortex | MCP server | 76 | yesterday | MIT | A | — | Claude Code |
| data-olympusknaisoma/data-olympus | MCP server | 30 | yesterday | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| neverinfamous-memory-journal-mcpneverinfamous/memory-journal-mcp | MCP server | 20 | 4d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| fidelis-memoryhermes-labs-ai/fidelis | MCP server | 25 | 18d ago | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| rag-ratcq27-dev/rag-rat | MCP server | 26 | 28d ago | MIT | A | — | Claude Code |
| cgr-captureGNS-Foundation/grafomem | MCP server | 3 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |