A side-by-side look at the Verified Memory and Claude Soul MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Verified Memory for knowledge & memory work as a local process; choose Claude Soul for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
V
Choose Verified Memory when
You need dedicated capabilities in the Knowledge & Memory domain.
No tool names declared yet. Check the project README from the listing page.
Claude Soul 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 is categorized under Knowledge & Memory and uses a local stdio subprocess. Claude Soul belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Verified Memory for knowledge & memory work and Claude Soul 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.
Verified Memory is listed as free. Auth: no auth required. Claude Soul 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 domdemetz-claude-soul 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. Claude Soul has 57/100 (Good) with 2 views, 0 installs and 91 GitHub stars.