Verified Memory vs Vestige
A side-by-side look at the Verified Memory and Vestige MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
Verified MemoryKnowledge & Memory · Local subprocess (stdio)Offline read-only search over a checksum-verified, optionally signed memory pack, with exact quotes45FairAuth: no auth requiredVerdict: choose Verified Memory for knowledge & memory work as a local process; choose Vestige for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
VChoose Verified Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Vestige when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Verified Memory | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 45/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 645 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Verified Memory | View Vestige |
Tools & capabilities
Verified Memory tools
No tool names declared yet. Check the project README from the listing page.
Vestige tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Verified Memory
{
"mcpServers": {
"verified-memory": {
"command": "npx",
"args": [
"-y",
"@python1/verified-memory-mcp"
]
}
}
}
Vestige
No confirmed install command for Vestige yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Verified Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Vestige belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Verified Memory for knowledge & memory work and Vestige for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Vestige has no confirmed install command yet — follow its own setup instructions.
Verified Memory is listed as free. Auth: no auth required. Vestige is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add verified-memory and samvallad33-vestige as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Verified Memory has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Vestige has 52/100 (Good) with 3 views, 0 installs and 645 GitHub stars.