# Verified Memory (npm · @python1/verified-memory-mcp)

Offline read-only search over a checksum-verified, optionally signed memory pack, with exact quotes

- Trust score: 33/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@python1/verified-memory-mcp`: 33/100 (this document), [markdown](https://verifymcp.io/servers/python1-verified-memory/python1-verified-memory-mcp.md), [page](https://verifymcp.io/servers/python1-verified-memory/python1-verified-memory-mcp)

## Channel facts

- Registry: `npm`
- Package: `@python1/verified-memory-mcp`
- Version: `0.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 4.3.6, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

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

## Install

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

Verified Memory runs locally as an npm package, launched with npx -y @python1/verified-memory-mcp. 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 python1-verified-memory -- npx -y @python1/verified-memory-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "python1-verified-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@python1/verified-memory-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "python1-verified-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@python1/verified-memory-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add python1-verified-memory -- npx -y @python1/verified-memory-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add python1-verified-memory --command npx --arg -y --arg @python1/verified-memory-mcp
```

### Hermes

```yaml
mcp_servers:
  python1-verified-memory:
    command: "npx"
    args: ["-y", "@python1/verified-memory-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "python1-verified-memory": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@python1/verified-memory-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add python1-verified-memory -t stdio -c npx -a -y @python1/verified-memory-mcp
```

### Other

```json
{
  "mcpServers": {
    "python1-verified-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@python1/verified-memory-mcp"
      ]
    }
  }
}
```

## 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-10-24 (score 33, −5)

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

### 2026-10-18 (score 38, 0)

- [functional] Package version: 0.4.0 → 0.4.1

### 2026-10-17 (score 38, 0)

- [functional] Package version: 0.3.0 → 0.4.0

### 2026-10-14 (score 38, +10)

- [security improvement] Known CVEs: unverified → pass
- [security] Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- [functional improvement] Dependency health: unverified → 0.85
- [functional] Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.

### 2026-10-13 (score 28, −10)

- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional] Package version: 0.1.0 → 0.3.0
- [functional] Package version: 0.1.0 → 0.2.0

### 2026-10-12 (score 38)

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, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/python1-verified-memory/python1-verified-memory-mcp#diagnostics

## Score history

- 2026-11-05: 33
- 2026-11-04: 33
- 2026-11-03: 33
- 2026-11-02: 33
- 2026-11-01: 33
- 2026-10-31: 33
- 2026-10-30: 33
- 2026-10-29: 33
- 2026-10-28: 33
- 2026-10-27: 33
- 2026-10-26: 33
- 2026-10-25: 33
- 2026-10-24: 33
- 2026-10-23: 38
- 2026-10-22: 38
- 2026-10-21: 38
- 2026-10-20: 38
- 2026-10-19: 38
- 2026-10-18: 38
- 2026-10-17: 38
- 2026-10-16: 38
- 2026-10-15: 38
- 2026-10-14: 38
- 2026-10-13: 28
- 2026-10-12: 38

## Common questions

### What is the Verified Memory MCP server?

Verified Memory is an MCP server listed in the public MCP registry as io.github.python1/verified-memory. Offline read-only search over a checksum-verified, optionally signed memory pack, with exact quotes. This page covers its npm package (@python1/verified-memory-mcp).

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

Verified Memory scores 33 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.

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

Verified Memory 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.

### What licence is the Verified Memory MCP server under?

Verified Memory 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/@python1/verified-memory-mcp
- Socket report: https://socket.dev/npm/package/@python1/verified-memory-mcp
- Repository: https://github.com/python1/data-lore-hive
- Changelog RSS feed: https://verifymcp.io/servers/python1-verified-memory/python1-verified-memory-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/python1-verified-memory/python1-verified-memory-mcp.json
- HTML version of this page: https://verifymcp.io/servers/python1-verified-memory/python1-verified-memory-mcp