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.

Memento

OCI · GHCR.IO/SCRYPSTER/MEMENTO:0.1.0 · SCANNED SEP 20

Persistent memory for AI tools. Local-first knowledge graph with hybrid search.

−4 this week 5 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 & Transparency26
  • 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
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Memento MCP server?

Memento runs locally as a container image, launched with docker run --rm -i ghcr.io/scrypster/memento:0.1.0. 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/scrypster/memento:0.1.0

# add to Claude Code
claude mcp add scrypster-memento -- docker run --rm -i ghcr.io/scrypster/memento:0.1.0
// .cursor/mcp.json
{
  "mcpServers": {
    "scrypster-memento": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/scrypster/memento:0.1.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "scrypster-memento": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/scrypster/memento:0.1.0"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add scrypster-memento -- docker run --rm -i ghcr.io/scrypster/memento:0.1.0
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "scrypster-memento": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/scrypster/memento:0.1.0"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  scrypster-memento:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/scrypster/memento:0.1.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "scrypster-memento": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/scrypster/memento:0.1.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "scrypster-memento": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/scrypster/memento:0.1.0"
      ]
    }
  }
}
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.

  • 17 Sept 26 −4
    • Provenance: fail → unverified security
    • License: pass → unverified functional
    • Maintenance: pass → unverified functional
    • Licence: MIT functional
  • 15 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 8 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 6 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 2 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 1 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 30 Aug 26 0
    • Security disclosure: unverified → fail 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 21 Sept 2026 · Analysed oci/ghcr.io/scrypster/memento:0.1.0

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.

Common questions

What is the Memento MCP server?

Memento is an MCP server listed in the public MCP registry as io.github.scrypster/memento. Persistent memory for AI tools. Local-first knowledge graph with hybrid search. This page covers its container image (ghcr.io/scrypster/memento:0.1.0).

Is the Memento MCP server safe to use?

Memento scores 5 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Memento MCP server still maintained?

Memento is still listed as active in the MCP registry. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.