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/agentkitai/loreWrote 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/agentkitai/lore/lore)<a href="https://agentmods.dev/mcp/agentkitai/lore/lore"><img src="https://agentmods.dev/badge/mcp/agentkitai/lore/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/agentkitai/lore/lore"><img src="https://agentmods.dev/badge/mcp/agentkitai/lore/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 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
{
"lore": {
"command": "uvx",
"args": [
"lore-sdk",
"lore-sdk[mcp]"
],
"env": {}
}
}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 · 10 lines scan A 91b43a5f8c3d
lore is an MCP server published in the GitHub repository agentkitai/lore (9 stars, last pushed 6d 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
a-memory
a-memory — persistent, layer-isolated memory for AI agents: 5 primitives, hybrid search, knowledge graphs, envelope encryption. Runs locally from the a-memory Python package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
engram
Ranked local code-graph context for AI coding agents. Intercepts reads + greps. Apache-2.0. Runs locally from the engramx npm package. Needs 5 environment variables to run.
chatcrystal
Local-first AI PKM memory for coding conversations. Runs locally from the chatcrystal npm package. Needs 2 environment variables to run.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
mitos
Architectural decision memory for LLM-native workflows — markdown for humans, a graph for agents. Runs locally from the mitos-adr Python package.