io.github.LeandroPG19/cuba-memorys
PYPI · CUBA-MEMORYS · 2 COMPONENTS · SCANNED SEP 20
Persistent memory MCP server. 28 tools, BM25+MMR+OOD retrieval, tamper-evident audit, code graph.
Available components
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 Security88
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency23
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
Unverified: 5 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 →
How do I install the io.github.LeandroPG19/cuba-memorys MCP server?
io.github.LeandroPG19/cuba-memorys runs locally as a PyPI package, launched with uvx cuba-memorys. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cuba-memorys
claude mcp add leandropg19-cuba-memorys -- uvx cuba-memorys
{
"mcpServers": {
"leandropg19-cuba-memorys": {
"command": "uvx",
"args": [
"cuba-memorys"
]
}
}
} {
"servers": {
"leandropg19-cuba-memorys": {
"command": "uvx",
"args": [
"cuba-memorys"
]
}
}
} codex mcp add leandropg19-cuba-memorys -- uvx cuba-memorys
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leandropg19-cuba-memorys": {
"type": "local",
"command": [
"uvx",
"cuba-memorys"
],
"enabled": true
}
}
} openclaw mcp add leandropg19-cuba-memorys --command uvx --arg cuba-memorys
mcp_servers:
leandropg19-cuba-memorys:
command: "uvx"
args: ["cuba-memorys"] {
"McpServers": {
"leandropg19-cuba-memorys": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"cuba-memorys"
]
}
}
} assistant mcp add leandropg19-cuba-memorys -t stdio -c uvx -a cuba-memorys
{
"mcpServers": {
"leandropg19-cuba-memorys": {
"command": "uvx",
"args": [
"cuba-memorys"
]
}
}
} 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 +10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Aug 26 0
- Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
- Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
- Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
- 16 Aug 26 0
- Malware scan: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- 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
- 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
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Package version: 1.25.0 → 1.26.0 functional
- 15 Aug 26 0
- Malware scan: unverified → pass ▲ security
- 14 Aug 26 0
- Malware scan: pass → unverified ▼ security
- Package version: 1.24.0 → 1.25.0 functional
- 13 Aug 26 0
- Package version: 1.23.0 → 1.24.0 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
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 pypi/cuba-memorys@1.26.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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.
What is the io.github.LeandroPG19/cuba-memorys MCP server?
io.github.LeandroPG19/cuba-memorys is an MCP server listed in the public MCP registry as io.github.LeandroPG19/cuba-memorys. Persistent memory MCP server. 28 tools, BM25+MMR+OOD retrieval, tamper-evident audit, code graph. This page covers its PyPI package (cuba-memorys).
Is the io.github.LeandroPG19/cuba-memorys MCP server safe to use?
io.github.LeandroPG19/cuba-memorys scores 31 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.LeandroPG19/cuba-memorys MCP server still maintained?
io.github.LeandroPG19/cuba-memorys is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.LeandroPG19/cuba-memorys MCP server under?
io.github.LeandroPG19/cuba-memorys declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.