Perseus Vault — Persistent Memory for Claude
Persistent, deterministic memory for AI agents. They guess, we remember. 122 canonical MCP tools: remember, recall, search, link entities, bi-temporal journal + audit trail, state management, AES-256-GCM encryption enabled by default. Local-first, single Rust binary, zero cloud dependencies.
- Category
- AI
- Primary Subcategory
- Pending
Integration details
Description
Perseus Vault gives Claude durable memory across sessions. It is a single Rust binary with an embedded SQLite database — no Docker, no Postgres, no cloud. Features include: - **122 canonical MCP tools** for entity storage, hybrid search (FTS5 + dense vector), knowledge-graph traversal, journal audit trail, and state management - **AES-256-GCM encryption at rest enabled by default** for fresh installations - **Fully local** — never phones home, no telemetry, air-gapped by default - **Agent-first design** — entity lifecycle with Ebbinghaus decay, auto-promotion, archiving - **Works with any MCP host** — Claude Desktop, Claude Code, Cursor, Hermes Agent, Perseus, and more Install in one line: `curl -sSf https://raw.githubusercontent.com/Perseus-Computing-LLC/perseus-vault/main/scripts/install.sh | sh`
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Perseus Computing
- Access
- Unknown
- First tracked
- 2026-07-20
- Tool count
- 0
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Perseus Vault — Persistent Memory for Claude isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures

Remote Connectors Claude can surface from the Connector picker.
About Claude's Discoverability Score
Your Connector now competes to appear for users’ prompts
Competitive lineup
0 tools agents can invoke
No tools are exposed by this Claude Connector in the latest snapshot.
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.
