Mnemosyne
NPM · MNEMOSY-AI
Evidence-tracked local memory MCP server: one SQLite file; corrections retire dependent memories.
Available components
Last scanned (19 hours ago)
Scores higher than 29% of npm servers
Category Memory and Knowledge
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 10 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to 28naem-del/mnemosyne). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →
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.
- 29 Oct 26 50
First indexed and scored.
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 4 Nov 2026 · Analysed npm/mnemosy-ai@3.0.0-rc.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | 28naem-del/mnemosyne |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/28naem-del/mnemosyne/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3573329825 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bea403fdca0638903f8fa60df26c8dedfa9a493299c9218ab8dadfb74fe4a36b1ef9443b8ba21b869e9dd1250669670c8ee82a877ca32be76973d5a8f |
Background: How many MCP packages publish verified provenance →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| Stale | 10 |
| 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.
How do I install the Mnemosyne MCP server?
Mnemosyne runs locally as an npm package, launched with npx -y mnemosy-ai. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mnemosy-ai
claude mcp add 28naem-del-mnemosyne -- npx -y mnemosy-ai
What is the Mnemosyne MCP server?
Mnemosyne is an MCP server listed in the public MCP registry as io.github.28naem-del/mnemosyne. Evidence-tracked local memory MCP server: one SQLite file; corrections retire dependent memories. This page covers its npm package (mnemosy-ai).
Is the Mnemosyne MCP server safe to use?
Mnemosyne scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Mnemosyne MCP server still maintained?
Mnemosyne is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Mnemosyne MCP server under?
Mnemosyne declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.