cuba-memorys
npm
v0.24.0
Published by leandropg19 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Persistent memory MCP server (v0.15) — 29 tools, PostgreSQL + pgvector, bitemporal facts, BM25+RRF hybrid search, graph metrics/communities, Hebbian learning, episodic memory, audit log, project scoping, tree-sitter codegraph.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`npm/bin.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } = require("child_process"); const path = require("path"); const fs = require("fs"); const { ensureBinary }
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server npm/bin.js
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/gen-eval-dataset.py:51`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: "" try: p = subprocess.run( ["claude", "--model", MODEL, "--print", "--output-format", "json"],
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/gen-eval-dataset.py
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/mcp_live_session_test.py:81`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: c") self.proc = subprocess.Popen( [str(BINARY)], stdin=subprocess.PIPE, stdo
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/mcp_live_session_test.py
"cuba-memorys" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node npm/postinstall.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package cuba-memorys
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.24.0 latest |
A 92/100 | 4 | 1.13.0 | 2026-09-07 |
v0.23.0 |
A 92/100 | 4 | 1.12.1 | 2026-08-16 |
v0.22.0 |
A 92/100 | 4 | 1.12.1 | 2026-08-14 |
v0.21.0 |
A 92/100 | 4 | 1.12.1 | 2026-08-12 |
v0.20.0 |
A 92/100 | 4 | 1.12.1 | 2026-08-03 |
v0.18.0 |
A 92/100 | 4 | 1.12.1 | 2026-07-29 |
v0.15.0 |
A 92/100 | 4 | 1.12.1 | 2026-07-28 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan cuba-memorys --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
Security scan results for the A5sql MCP server.
Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.
MCP server for Aiven cloud data platform - manage PostgreSQL, Kafka, and other services
MCP Server for All-Inkl.com hosting via KAS API
Structured aquarium, marine, terrarium and paludarium data for AI agents.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.