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

io.github.LeandroPG19/cuba-memorys

NPM · CUBA-MEMORYS · 2 COMPONENTS · SCANNED AUG 3

Persistent memory MCP server. 29 tools, BM25+MMR+OOD retrieval, tamper-evident audit, code graph.

Available components

npm · cuba-memorys 37 pypi · cuba-memorys 35
−8 this week 37 Trust /100
Trust breakdown (6 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 →

Supply Chain Security94
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
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
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · cuba-memorys

# add to Claude Code
claude mcp add leandropg19-cuba-memorys -- npx -y cuba-memorys
# add to Codex CLI
codex mcp add leandropg19-cuba-memorys -- npx -y cuba-memorys
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "leandropg19-cuba-memorys": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cuba-memorys"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add leandropg19-cuba-memorys --command npx --arg -y --arg cuba-memorys
# ~/.hermes/config.yaml
mcp_servers:
  leandropg19-cuba-memorys:
    command: "npx"
    args: ["-y", "cuba-memorys"]
// mcp.json
{
  "mcpServers": {
    "leandropg19-cuba-memorys": {
      "command": "npx",
      "args": [
        "-y",
        "cuba-memorys"
      ]
    }
  }
}
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.

  • 3 Aug 26 0
    • Licence: AGPL-3.0-only → Apache-2.0 functional
    • Package version: 0.20.0 → 0.21.0 functional
  • 2 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Jul 26 −5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • Package version: 0.19.0 → 0.20.0 functional
  • 29 Jul 26 0
    • Package version: 0.17.1 → 0.19.0 functional
    • Package version: 0.17.1 → 0.18.0 functional
  • 28 Jul 26 −18
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.15.0 → 0.17.1 functional
    • Package version: 0.15.0 → 0.17.0 functional
    • Package version: 0.15.0 → 0.16.0 functional
  • 27 Jul 26 0
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • 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
  • 26 Jul 26 45

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Install scripts 1 script
Hook Tier Command
postinstall unreviewed node npm/postinstall.js
Dependencies 0 packages

0 packages in the resolved dependency tree.

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.

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.