State Memory MCP vs Vestige
Two MCP servers from our memory ranking, compared on live data - updated nightly, never sponsored.
Bottom line · 2026-09-30
State Memory MCP records significantly more monthly package installs (25,593 vs 2,065); both are actively maintained, with commits inside the last month.
How they differ in kind
State Memory MCP focuses on: @putervision/state-memory-mcp is a zero-infrastructure, deterministic Model Context Protocol (MCP) server that provides AI coding assistants (such as Cursor, Claude Code, Gemini, or Copilot) with a… Vestige focuses on: Local memory for MCP agents, on a signed log. Implementation languages differ (TypeScript vs Rust).
What each one does
State Memory MCP
@putervision/state-memory-mcp is a zero-infrastructure, deterministic Model Context Protocol (MCP) server that provides AI coding assistants (such as Cursor, Claude Code, Gemini, or Copilot) with a structured, persistent SQLite graph for tracking workflow state - tasks, decisions, artifacts, plans, blockers, and their semantic relationships. It runs locally over stdio via the published package.
From the project's README.
Vestige
Local memory for MCP agents, on a signed log. It keeps the decisions a project already made, and it can walk a failure backward along the links your memory actually recorded. Every write passes a gate and leaves a receipt. The store is Strata: an append-only, signed log on your machine.
From the project's README.
14 signals, side by side
| Signal | State Memory MCP | Vestige |
|---|---|---|
| Monthly installs | 25,593 | 2,065 |
| GitHub stars | 108 | 640 |
| Last commit | 2026-09-28 | 2026-09-30 |
| Releases · last 90 days | 4 | 10+ |
| In the registry since | Jul 2026 | May 2026 |
| Registry versions | 12 | 11 |
| Documented tools | not extracted - see README | not extracted - see README |
| Env vars extracted | none extracted - see README | none extracted - see README |
| Runs | local (stdio) | local (stdio) |
| Endpoint auth | local only | local only |
| Maintenance | actively maintained | actively maintained |
| License | MIT | AGPL-3.0 |
| Language | TypeScript | Rust |
| Category rank | #4 of 321 | #7 of 321 |
Which one, for what
Derived from the signals above, not hands-on testing.
Pick State Memory MCP if…
- → you want the more widely installed option - 25,593 monthly installs vs 2,065
- → you prefer a TypeScript codebase to extend or audit
Pick Vestige if…
- → release velocity matters - 10+ releases in 90 days vs 4
- → you prefer a Rust codebase to extend or audit
Who's behind them
State Memory MCP - putervision: 6 MCP servers tracked, 6 maintained, 304 combined stars. Full record.
Vestige - samvallad33: 1 MCP server tracked, 1 maintained, 640 combined stars.
Not sold on either?
The next-ranked memory servers we track:
Quick answers
Is State Memory MCP better than Vestige?
Package installs favor State Memory MCP: 25,593 monthly installs to 2,065. Vestige still ranks #7 of 321 maintained memory servers. Data as of 2026-09-30; we haven't hands-on tested either.
Can I use State Memory MCP and Vestige together?
Yes - MCP clients accept multiple servers in one config, so you can enable both memory servers side by side. If their tools overlap, keep the one whose toolset fits to keep your agent's tool list lean.
Keep exploring: best memory servers · TypeScript servers · Rust servers · all comparisons · every server
Methodology: package-usage signal = npm/PyPI installs (last month, platform APIs) · maintenance = commit recency + release cadence (GitHub) · tool lists and environment-variable names extracted from each project's README · endpoint auth from our own nightly probes. We haven't hand-tested these servers; everything here is data as of 2026-09-30.