Perseus Vault vs Vestige — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Perseus Vault vs Vestige
In-depth architectural comparison of the Perseus Vault and Vestige MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Perseus Vault
Knowledge & Memory · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Vestige
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Perseus Vault if you need specialized Knowledge & Memory tools running via a local process. Choose Vestige if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Perseus Vault when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: PERSEUS_VAULT_ENCRYPTION_KEY.
Primary tools included: Single Rust binary with embedded SQLite, AES-256-GCM encryption at rest, Hybrid BM25 full-text and dense vector search.
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Local SQLite storage with no cloud dependency, FSRS-6 spaced repetition scheduling for memory fading, Contradiction detection with claim_contradicts_memory status.
Local-first, MCP-native persistent memory for AI agents — a single Rust binary with embedded SQLite, hybrid FTS5 + dense-vector search, and optional AES-256-GCM encryption. Fully offline, no cloud.
Local-first cognitive memory for AI agents. FSRS-6 scheduling, smart ingest, SQLite storage, portable sync, embedded dashboard, and optional Cognitive Sandwich hooks for Claude Code, Cursor, Codex, and other MCP clients.
Category & Scope
Tools & Capabilities Breakdown
Perseus Vault Tools (6)
Single Rust binary with embedded SQLite
AES-256-GCM encryption at rest
Hybrid BM25 full-text and dense vector search
100 canonical MCP tools for memory operations
Offline, local-first with no cloud dependencies
Bi-temporal history and memory lifecycle management
Vestige Tools (6)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Perseus Vault is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Vestige belongs to Knowledge & Memory using local stdio subprocess. Select Perseus Vault when you need capabilities focused on knowledge & memory and Vestige when you require tools for knowledge & memory.