io.github.MinniAI-com/minnimemory
NPM · MINNIMEMORY
Curated, on-demand memory for AI coding agents. Cuts Claude Code token cost per session.
Available components
Last scanned (6 hours ago)
Scores higher than 35% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 619 tokens (~154/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +21
- Known CVEs: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 27 Oct 26 −20
- Known CVEs: fail → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 1.3.7 → 1.4.1 functional
- Package version: 1.3.7 → 1.4.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ 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 5 Nov 2026 · Analysed npm/minnimemory@1.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
apply Compile or re-apply ~165
Returns the command that writes the plan (backups first) and the operations it performs; this server never touches your disk. No drift: "nothing to apply". Refused on a credential-shaped source (no override over MCP), and on a compile that would not shrink the prefix unless force: true.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | token budget (default 60% of the file, at least 2000; a folder computes its own) |
| content | boolean | – | also return file contents, for a host without a shell |
| force | boolean | – | accept a compile that would not shrink the prefix |
| format | string | – | default text |
| target | string | – | folder in the root, "." for itself; none: the recorded memory folder; never guess |
No output schema declared.
No examples provided.
doctor Audit and preview ~143
Read-only, after init (refuses before it): the audit, drift since the last apply(), then the diff apply() would write. No target: the folder init recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | token budget (default 60% of the file, at least 2000; a folder computes its own) |
| diff | string | – | default summary; full adds the unified diff |
| force | boolean | – | preview the re-apply plan even with no drift |
| format | string | – | default text |
| target | string | – | folder in the root; "." = this project. Omitted: the memory folder in loaded, else what init recorded |
No output schema declared.
No examples provided.
init Map and preview ~152
First call. For the dev's memory set loaded from your context: your auto memory folder and each "Contents of <path>" file. Saves them, then maps, audits, previews.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | token budget (default 60% of the file, at least 2000; a folder computes its own) |
| diff | string | – | default summary; full adds the unified diff |
| force | boolean | – | preview the re-apply plan even with no drift |
| format | string | – | default text |
| loaded | object | – | – |
| target | string | – | folder in the root; "." = this project. Omitted: the memory folder in loaded, else what init recorded |
No output schema declared.
No examples provided.
undo Restore the original ~109
Returns the command that restores your original memory files and the operations it performs; this server never touches your disk. No compiled workspace: "nothing to undo".
| Name | Type | Req | Description |
|---|---|---|---|
| content | boolean | – | also return the originals' content, for a host without a shell |
| force | boolean | – | delete routed files even when edited since the last apply |
| format | string | – | default text |
| target | string | – | folder in the root, "." for itself; none: the recorded memory folder; never guess |
No output schema declared.
No examples provided.
How do I install the io.github.MinniAI-com/minnimemory MCP server?
io.github.MinniAI-com/minnimemory runs locally as an npm package, launched with npx -y minnimemory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · minnimemory
claude mcp add minniai-com-minnimemory -- npx -y minnimemory
What is the io.github.MinniAI-com/minnimemory MCP server?
io.github.MinniAI-com/minnimemory is an MCP server listed in the public MCP registry as io.github.MinniAI-com/minnimemory. Curated, on-demand memory for AI coding agents. Cuts Claude Code token cost per session. This page covers its npm package (minnimemory).
Is the io.github.MinniAI-com/minnimemory MCP server safe to use?
io.github.MinniAI-com/minnimemory scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.
What tools does the io.github.MinniAI-com/minnimemory MCP server expose?
io.github.MinniAI-com/minnimemory exposes 4 tools: init, doctor, apply, undo. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.
Is the io.github.MinniAI-com/minnimemory MCP server still maintained?
io.github.MinniAI-com/minnimemory is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.