VaultCrux Memory Core โ 32 tools: knowledge, decisions, constraints, signals, coverage
Connect Remote server
claude mcp add --transport http vaultcrux-memory-core https://api.vaultcrux.com/memory-core/mcp --header "x-api-key: <X_API_KEY>" --header "x-tenant-id: <X_TENANT_ID>" --header "x-agent-id: <X_AGENT_ID>"
{
"mcpServers": {
"vaultcrux-memory-core": {
"url": "https://api.vaultcrux.com/memory-core/mcp",
"headers": {
"x-api-key": "<X_API_KEY>",
"x-tenant-id": "<X_TENANT_ID>",
"x-agent-id": "<X_AGENT_ID>"
}
}
}
}
{
"servers": {
"vaultcrux-memory-core": {
"type": "http",
"url": "https://api.vaultcrux.com/memory-core/mcp",
"headers": {
"x-api-key": "<X_API_KEY>",
"x-tenant-id": "<X_TENANT_ID>",
"x-agent-id": "<X_AGENT_ID>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.vaultcrux.com/memory-core/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
x-api-keyRequired, secret | VaultCrux API key used to authorize Memory Core reads |
x-tenant-idRequired | VaultCrux tenant id used to scope Memory Core reads |
x-agent-idOptional | Optional agent id override for query and claim-check context |
Details
| Endpoint | https://api.vaultcrux.com/memory-core/mcp (Streamable HTTP) |
| First published | 25 Mar 2026 |
| Last updated | 25 Mar 2026 |
| Registry name | io.github.CueCrux/vaultcrux-memory-core |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
