Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Holographic Memory

PYPI · HOLOGRAPHIC-MEMORY-MCP · 2 COMPONENTS

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

−25 this week 10 Trust /100

Last scanned (7 hours ago)

Scores higher than 3% of PyPI servers

Category Memory and Knowledge

Degraded

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

Trust breakdown (7 categories)

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 Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: we could not find this package in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency3
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

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.

Changelog

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.

  • 5 Nov 26 −10
    • Malware scan: pass → unverified ▼ security
  • 4 Nov 26 −10

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

  • 3 Nov 26 −10

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

  • 2 Nov 26 −10

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

  • 1 Nov 26 0
    • Install scripts: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Provenance: pass → fail ▼ security
    • The code this package runs automatically changed: its declared build backend security
    • The attested source repository moved: writerslogic/holographic-memory security
    • Dependency health: pass → unverified ▼ functional
    • License: pass → fail ▼ functional
    • Maintenance: pass → fail ▼ functional
    • Security disclosure: unverified → pass ▲ functional
    • Licence: Apache-2.0 functional
  • 31 Oct 26 0
    • Source repository: pass → fail ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 35

    First indexed and scored.

Diagnostics

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 pypi/holographic-memory-mcp@0.1.2

Provenance Package not found

The registry answered that no such package exists, so no provenance could be looked up.

Result Package not found
Ecosystem pypi
Reason Metadata unavailable

Background: How many MCP packages publish verified provenance →

MCP tools

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 →

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.

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.

pypi · holographic-memory-mcp

# add to Claude Code
claude mcp add writerslogic-holographic-memory-mcp -- uvx holographic-memory-mcp
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.