Lore Context runs on your own machine — the client starts it, so there is no endpoint to ping. 25 installs a week from npm. Last commit 23 May 2026.
Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
result = subprocess.run(cmd, capture_output=True, text=True, check=False)
const out = execSync(`git diff --name-only ${since} HEAD`, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add lore-context-mcp -e 'LORE_API_URL=<LORE_API_URL>' -- npx -y @lore-context/server{
"mcpServers": {
"lore-context-mcp": {
"command": "npx",
"args": [
"-y",
"@lore-context/server"
],
"env": {
"LORE_API_URL": "<LORE_API_URL>"
}
}
}
}[mcp_servers.lore-context-mcp]
command = "npx"
args = ["-y", "@lore-context/server"]
env = { LORE_API_URL = "<LORE_API_URL>" }{
"mcpServers": {
"lore-context-mcp": {
"command": "npx",
"args": [
"-y",
"@lore-context/server"
],
"env": {
"LORE_API_URL": "<LORE_API_URL>"
}
}
}
}{
"servers": {
"lore-context-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@lore-context/server"
],
"env": {
"LORE_API_URL": "<LORE_API_URL>"
}
}
}
}Put your own value in place of
<LORE_API_URL> (Base URL of the Lore API that the MCP server should proxy tool calls to).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
LORE_API_KEY (Optional Lore API key when the API is configured to require authentication), LORE_MCP_TRANSPORT (MCP stdio transport implementation. Use sdk unless debugging legacy JSON-RPC mode).
Alternatives to Lore Context
same job, measured the same wayAppend-only event log for cross-agent context/memory sharing via 3 MCP tools.
Model inventory and governance: trace deployed models and their dependencies as an append-only log
Persistent memory for AI agents — log and recall conversation context over MCP.
Verifiable cognition: prove a session ledger is tamper-evident; audit & import any agent's logs.
Detect stale source context and retain traceable code-chain understanding for AI coding agents.
MCP server for Ordali memory: SQLite-backed project memory and governance traces.
Read-only semantic filtering, code search, log triage and traceable evidence for AI agents.
Causal memory and tamper-evident audit log for AI agents: log, why, search, time travel.
Lore Context — questions
Answers built from our own checks of this server.