VaultCrux Memory Core vs Configure Memory
VaultCrux Memory Core is an MCP server published by CueCrux. Marketplaces we read that list it: 1 (Official MCP Registry). Configure Memory is an MCP server published by configure-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Configure Memory | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 No figure published Not marked · First seen |
Listed Version: 3.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | VaultCrux Memory Core | Configure Memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.vaultcrux.com/memory-core/mcp) | Remote server (mcp.configure.dev) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cuecrux/vaultcrux | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-19 | Responded 4 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
VaultCrux Memory Core
VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage
Configure Memory
Bring your saved preferences, project decisions, and useful context into your next AI conversation.
How to run each
VaultCrux Memory Core As a remote MCP server
claude mcp add --transport http vaultcrux-memory-core https://api.vaultcrux.com/memory-core/mcp --header "x-api-key: <YOUR_X_API_KEY>" --header "x-tenant-id: <YOUR_X_TENANT_ID>"Requires: x-api-key header, x-tenant-id header
Configure Memory As a remote MCP server
claude mcp add --transport http configure-memory https://mcp.configure.dev/Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Configure Memory responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: VaultCrux Memory Core · What it can do: Configure Memory · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.