io.github.RecallWorks/recall
PYPI · AI-RECALLWORKS · SCANNED SEP 20
Open-source MCP memory server. Persistent, searchable, tiered memory across sessions.
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 Security74
- No malware found by supply-chain analysis.Pass
- A critical CVE affects chromadb, and no fixed version has been published yet. View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 8 of 85 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 134 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, 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.RecallWorks/recall MCP server?
io.github.RecallWorks/recall runs locally as a PyPI package, launched with uvx ai-recallworks. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ai-recallworks
claude mcp add recallworks-recall -- uvx ai-recallworks
{
"mcpServers": {
"recallworks-recall": {
"command": "uvx",
"args": [
"ai-recallworks"
]
}
}
} {
"servers": {
"recallworks-recall": {
"command": "uvx",
"args": [
"ai-recallworks"
]
}
}
} codex mcp add recallworks-recall -- uvx ai-recallworks
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"recallworks-recall": {
"type": "local",
"command": [
"uvx",
"ai-recallworks"
],
"enabled": true
}
}
} openclaw mcp add recallworks-recall --command uvx --arg ai-recallworks
mcp_servers:
recallworks-recall:
command: "uvx"
args: ["ai-recallworks"] {
"McpServers": {
"recallworks-recall": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"ai-recallworks"
]
}
}
} assistant mcp add recallworks-recall -t stdio -c uvx -a ai-recallworks
{
"mcpServers": {
"recallworks-recall": {
"command": "uvx",
"args": [
"ai-recallworks"
]
}
}
} 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
- 25 Aug 26 0
- CVE-2026-45833 affects this package: none ▼ security
- 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
- 8 Aug 26 0
- Security disclosure: fail → pass ▲ functional
- 4 Aug 26 0
- CVE-2026-45829 affects this package: none ▼ security
- Known CVEs: unverified → fail ▼ security
- Dependency health: unverified → 0.94 ▲ functional
- 2 Aug 26 0
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
- The scripts that run when this package is installed changed: build_backend security
- Security disclosure: fail → unverified ▼ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ 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
- Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. 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
- Licence: MIT functional
- 1 Aug 26 0
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- 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
- 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
- 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
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/ai-recallworks@0.5.2
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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2wm9-hf6c-p5cr | CVE-2026-45830 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| GHSA-36p7-vc44-83pf | CVE-2026-45833 | critical | no | |
| GHSA-f4j7-r4q5-qw2c | CVE-2026-45829 | critical | no | |
| GHSA-xph7-9rjv-w5fr | CVE-2026-45831 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| PYSEC-2026-311 | CVE-2026-45829 | none | no | |
| PYSEC-2026-3813 | CVE-2026-45830 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| PYSEC-2026-3814 | CVE-2026-45833 | none | no | |
| PYSEC-2026-3815 | CVE-2026-45831 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 85 packages
| Packages resolved | 85 |
|---|---|
| Stale | 8 |
| 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.RecallWorks/recall MCP server?
io.github.RecallWorks/recall is an MCP server listed in the public MCP registry as io.github.RecallWorks/recall. Open-source MCP memory server. Persistent, searchable, tiered memory across sessions. This page covers its PyPI package (ai-recallworks).
Is the io.github.RecallWorks/recall MCP server safe to use?
io.github.RecallWorks/recall scores 32 out of 100 on VerifyMCP. We recorded 8 known advisories against 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.RecallWorks/recall MCP server still maintained?
io.github.RecallWorks/recall 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.RecallWorks/recall MCP server under?
io.github.RecallWorks/recall declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.