# Holographic Memory (pypi · holographic-memory-mcp)

Local persistent memory for AI agents with recall, search, forgetting, and encrypted storage.

- Trust score: 10/100 (low)
- Change this week: −25
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-11-05

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- npm · `holographic-memory-mcp`: 44/100, [markdown](https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp.md), [page](https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp)
- pypi · `holographic-memory-mcp`: 10/100 (this document), [markdown](https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp-2.md), [page](https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp-2)

## Channel facts

- Registry: `pypi`
- Package: `holographic-memory-mcp`
- Version: `0.1.2`
- 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**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: we could not find this package in its registry.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we could not find this package in its registry.
- **Provenance & Transparency**: 3/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: the registry has no such package, so there's no artefact to verify.
  - License check failed: the registry has no such package, so no license can be read.
  - Maintenance check failed: the registry has no such package, so there's no release history to read.
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

Holographic Memory runs locally as a PyPI package, launched with uvx holographic-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 writerslogic-holographic-memory-mcp -- uvx holographic-memory-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "writerslogic-holographic-memory-mcp": {
      "command": "uvx",
      "args": [
        "holographic-memory-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "writerslogic-holographic-memory-mcp": {
      "command": "uvx",
      "args": [
        "holographic-memory-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add writerslogic-holographic-memory-mcp -- uvx holographic-memory-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "writerslogic-holographic-memory-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "holographic-memory-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add writerslogic-holographic-memory-mcp --command uvx --arg holographic-memory-mcp
```

### Hermes

```yaml
mcp_servers:
  writerslogic-holographic-memory-mcp:
    command: "uvx"
    args: ["holographic-memory-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "writerslogic-holographic-memory-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "holographic-memory-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add writerslogic-holographic-memory-mcp -t stdio -c uvx -a holographic-memory-mcp
```

### Other

```json
{
  "mcpServers": {
    "writerslogic-holographic-memory-mcp": {
      "command": "uvx",
      "args": [
        "holographic-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-11-05 (score 10, −10)

- [security regression] Malware scan: pass → unverified

### 2026-11-04 (score 20, −10)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-03 (score 30, −10)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-02 (score 40, −10)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-01 (score 50, 0)

- [security regression] Install scripts: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [security regression] Provenance: pass → fail
- [security] The code this package runs automatically changed: its declared build backend
- [security] The attested source repository moved: writerslogic/holographic-memory
- [functional regression] Dependency health: pass → unverified
- [functional regression] License: pass → fail
- [functional regression] Maintenance: pass → fail
- [functional improvement] Security disclosure: unverified → pass
- [functional] Licence: Apache-2.0

### 2026-10-31 (score 50, 0)

- [security regression] Source repository: pass → fail
- [functional regression] Security disclosure: pass → unverified

### 2026-10-30 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 35)

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. The full working is on the page: https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp-2#diagnostics

## Score history

- 2026-11-05: 10
- 2026-11-04: 20
- 2026-11-03: 30
- 2026-11-02: 40
- 2026-11-01: 50
- 2026-10-31: 50
- 2026-10-30: 50
- 2026-10-29: 35
- 2026-10-28: 35
- 2026-10-27: 35
- 2026-10-26: 35

## Common questions

### What is the Holographic Memory MCP server?

Holographic Memory is an MCP server listed in the public MCP registry as io.github.writerslogic/holographic-memory-mcp. Local persistent memory for AI agents with recall, search, forgetting, and encrypted storage. This page covers its PyPI package (holographic-memory-mcp).

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

Holographic Memory scores 10 out of 100 on VerifyMCP. 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 Holographic Memory MCP server still maintained?

Holographic Memory is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 30 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Holographic Memory MCP server?

VerifyMCP ran 5 checks on Holographic Memory, covering Source repository, Provenance, License, Maintenance and 1 more. 9 items could not be completed, a gap on our side rather than a finding about Holographic Memory: Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/holographic-memory-mcp/
- Socket report: https://socket.dev/pypi/package/holographic-memory-mcp
- Website: https://holographic-memory.com/
- Changelog RSS feed: https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/writerslogic-holographic-memory-mcp/holographic-memory-mcp-2