# io.github.MinniAI-com/minnimemory (npm · minnimemory)

Curated, on-demand memory for AI coding agents. Cuts Claude Code token cost per session.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `minnimemory`: 68/100 (this document), [markdown](https://verifymcp.io/servers/minniai-com-minnimemory/minnimemory.md), [page](https://verifymcp.io/servers/minniai-com-minnimemory/minnimemory)

## Channel facts

- Registry: `npm`
- Package: `minnimemory`
- Version: `1.4.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - 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.
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add minniai-com-minnimemory -- npx -y minnimemory
```

### Cursor

```json
{
  "mcpServers": {
    "minniai-com-minnimemory": {
      "command": "npx",
      "args": [
        "-y",
        "minnimemory"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "minniai-com-minnimemory": {
      "command": "npx",
      "args": [
        "-y",
        "minnimemory"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add minniai-com-minnimemory -- npx -y minnimemory
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "minniai-com-minnimemory": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "minnimemory"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add minniai-com-minnimemory --command npx --arg -y --arg minnimemory
```

### Hermes

```yaml
mcp_servers:
  minniai-com-minnimemory:
    command: "npx"
    args: ["-y", "minnimemory"]
```

### Netclaw

```json
{
  "McpServers": {
    "minniai-com-minnimemory": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "minnimemory"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add minniai-com-minnimemory -t stdio -c npx -a -y minnimemory
```

### Other

```json
{
  "mcpServers": {
    "minniai-com-minnimemory": {
      "command": "npx",
      "args": [
        "-y",
        "minnimemory"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 68, +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.

### 2026-11-02 (score 67, +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.

### 2026-10-30 (score 66, +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.

### 2026-10-28 (score 65, +21)

- [security regression] Known CVEs: unverified → fail
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-10-27 (score 44, −20)

- [security regression] Known CVEs: fail → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional] Package version: 1.3.7 → 1.4.1
- [functional] Package version: 1.3.7 → 1.4.0

### 2026-10-26 (score 64, +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.

### 2026-10-24 (score 63, −4)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 67, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

## MCP tools (4)

### `init` (~152 tokens)

Map and preview

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.

Input parameters:

- `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

### `doctor` (~143 tokens)

Audit and preview

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.

Input parameters:

- `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

### `apply` (~165 tokens)

Compile or re-apply

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.

Input parameters:

- `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

### `undo` (~109 tokens)

Restore the original

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".

Input parameters:

- `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

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/minniai-com-minnimemory/minnimemory#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 65
- 2026-10-28: 65
- 2026-10-27: 44
- 2026-10-26: 64
- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 67
- 2026-10-22: 56

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/minnimemory
- Socket report: https://socket.dev/npm/package/minnimemory
- Repository: https://github.com/MinniAI-com/minnimemory-plugin
- Website: https://minniai.com/minnimemorymcp
- Changelog RSS feed: https://verifymcp.io/servers/minniai-com-minnimemory/minnimemory.xml
- Changelog JSON feed: https://verifymcp.io/servers/minniai-com-minnimemory/minnimemory.json
- HTML version of this page: https://verifymcp.io/servers/minniai-com-minnimemory/minnimemory