VaultCrux Memory Core
io.github.CueCrux/vaultcrux-memory-coreVersion 0.2.0VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage
Status
Not reachableWe could not connect (DNS, network or TLS).- Last checked
- Nov 14, 2026, 14:36 UTC
- Latency
- Not measured
- Remotes responding
- 0 of 1
- Sign-in
- API key
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.vaultcrux.com/memory-core/mcpNot reachableNo sign-in
Claude Code
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>'Replace <YOUR_X_API_KEY>, <YOUR_X_TENANT_ID> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: vaultcrux-memory-core
Remote MCP server URL: https://api.vaultcrux.com/memory-core/mcp
This server expects the header x-api-key, x-tenant-id.Cursor
{
"mcpServers": {
"vaultcrux-memory-core": {
"url": "https://api.vaultcrux.com/memory-core/mcp",
"headers": {
"x-api-key": "<YOUR_X_API_KEY>",
"x-tenant-id": "<YOUR_X_TENANT_ID>"
}
}
}
}Replace <YOUR_X_API_KEY>, <YOUR_X_TENANT_ID> before running.
VS Code
code --add-mcp '{"name":"vaultcrux-memory-core","type":"http","url":"https://api.vaultcrux.com/memory-core/mcp","headers":{"x-api-key":"<YOUR_X_API_KEY>","x-tenant-id":"<YOUR_X_TENANT_ID>"}}'Replace <YOUR_X_API_KEY>, <YOUR_X_TENANT_ID> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
No tool list available.
Details
- Registry status
- Active
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Website
- Not given
- Categories (suggested)
- Knowledge and notesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared