# Memory Vault (npm · memory-vault)

Claude-style memory over a local folder via MCP — per-project spaces plus a shared org layer.

- Trust score: 34/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-23

## Components

- npm · `memory-vault`: 34/100 (this document), [markdown](https://verifymcp.io/servers/apurv101-memory-vault/memory-vault.md), [page](https://verifymcp.io/servers/apurv101-memory-vault/memory-vault)

## Channel facts

- Registry: `npm`
- Package: `memory-vault`
- Version: `0.3.1`
- Transport: `streamable-http`

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

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.

**Unverified: 4 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.

## Install

### How do I install the Memory Vault MCP server?

Memory Vault runs locally as an npm package, launched with npx -y memory-vault. 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 apurv101-memory-vault -- npx -y memory-vault
```

### Cursor

```json
{
  "mcpServers": {
    "apurv101-memory-vault": {
      "command": "npx",
      "args": [
        "-y",
        "memory-vault"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "apurv101-memory-vault": {
      "command": "npx",
      "args": [
        "-y",
        "memory-vault"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add apurv101-memory-vault -- npx -y memory-vault
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add apurv101-memory-vault --command npx --arg -y --arg memory-vault
```

### Hermes

```yaml
mcp_servers:
  apurv101-memory-vault:
    command: "npx"
    args: ["-y", "memory-vault"]
```

### Netclaw

```json
{
  "McpServers": {
    "apurv101-memory-vault": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "memory-vault"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add apurv101-memory-vault -t stdio -c npx -a -y memory-vault
```

### Other

```json
{
  "mcpServers": {
    "apurv101-memory-vault": {
      "command": "npx",
      "args": [
        "-y",
        "memory-vault"
      ]
    }
  }
}
```

## 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-08-22 (score 34, 0)

- [functional] Package version: 0.2.2 → 0.3.1

### 2026-08-20 (score 34, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-19 (score 19)

First indexed and scored.

## MCP tools (0)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/apurv101-memory-vault/memory-vault#diagnostics

## Score history

- 2026-08-23: 34
- 2026-08-22: 34
- 2026-08-21: 34
- 2026-08-20: 34
- 2026-08-19: 19

## Common questions

### What is the Memory Vault MCP server?

Memory Vault is an MCP server listed in the public MCP registry as io.github.apurv101/memory-vault. Claude-style memory over a local folder via MCP, per-project spaces plus a shared org layer. This page covers its npm package (memory-vault).

### Is the Memory Vault MCP server safe to use?

Memory Vault scores 34 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 August 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.

### Is the Memory Vault MCP server still maintained?

Memory Vault is still listed as active in the MCP registry. We last reached this channel on 23 August 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 Memory Vault MCP server under?

Memory Vault declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/memory-vault
- Socket report: https://socket.dev/npm/package/memory-vault
- Changelog RSS feed: https://verifymcp.io/servers/apurv101-memory-vault/memory-vault.xml
- Changelog JSON feed: https://verifymcp.io/servers/apurv101-memory-vault/memory-vault.json
- HTML version of this page: https://verifymcp.io/servers/apurv101-memory-vault/memory-vault