Vestige vs Statelessagent — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vestige vs Statelessagent
In-depth architectural comparison of the Vestige and Statelessagent 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
Vestige
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Statelessagent
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Vestige if you need specialized Knowledge & Memory tools running via a local process. Choose Statelessagent 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 Vestige 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).
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.
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Primary tools included: Provenance tracking and stale knowledge detection, Dual-layer memory with atomic fact extraction, 19 MCP tools for session handoffs, decisions, and search.
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.
Memory with provenance tracking — records where agent knowledge originated and detects when sources change. 17 MCP tools for session handoffs, decisions, semantic search, and knowledge graph. Works across Claude Code, Cursor, Windsurf, Codex CLI, and Gemini CLI. Single Go binary, SQLite + vector search, fully local.
Category & Scope
Tools & Capabilities Breakdown
Vestige Tools (6)
Local SQLite storage with no cloud dependency
FSRS-6 spaced repetition scheduling for memory fading
Contradiction detection with claim_contradicts_memory status
Backward causal memory reach and contrast analysis
Embedded dashboard for monitoring and visualization
Prebuilt single 25MB Rust binary for multiple OS
Statelessagent 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).
Vestige is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Statelessagent belongs to Knowledge & Memory using local stdio subprocess. Select Vestige when you need capabilities focused on knowledge & memory and Statelessagent when you require tools for knowledge & memory.