Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lore Context

OCI · GHCR.IO/LORE-CONTEXT/LORE-CONTEXT-MCP:0.6.0-ALPHA.1 · 2 COMPONENTS · SCANNED SEP 20

Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.

Available components

npm · @lore-context/server 80 oci · ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1 6
0 this week 6 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: we could not reach the registry to check. This is a gap on our side.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we could not reach the registry to check. This is a gap on our side.Unverified
Provenance & Transparency29
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance not yet verified. View diagnostics → Unverified
  • License not yet determined.Unverified
  • Maintenance history not yet determined.Unverified
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Lore Context MCP server?

Lore Context runs locally as a container image, launched with docker run --rm -i ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1

# add to Claude Code
claude mcp add lore-context-lore-context-mcp -- docker run --rm -i ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1
// .cursor/mcp.json
{
  "mcpServers": {
    "lore-context-lore-context-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lore-context-lore-context-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add lore-context-lore-context-mcp -- docker run --rm -i ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lore-context-lore-context-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  lore-context-lore-context-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lore-context-lore-context-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "lore-context-lore-context-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • Security disclosure: fail → pass ▲ functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 0
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
  • 26 Jul 26 0

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed oci/ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem oci
Reason No trust root

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.