NestDaddy

VaultCrux Memory Core

io.github.CueCrux/vaultcrux-memory-core ยท v0.2.0

VaultCrux Memory Core โ€” 32 tools: knowledge, decisions, constraints, signals, coverage

Connect Remote server

Terminal
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>"
~/.cursor/mcp.json
{
  "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>"
      }
    }
  }
}
.vscode/mcp.json
{
  "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>"
      }
    }
  }
}
Claude Desktop
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

NameDescription
x-api-key
Required, secret
VaultCrux API key used to authorize Memory Core reads
x-tenant-id
Required
VaultCrux tenant id used to scope Memory Core reads
x-agent-id
Optional
Optional agent id override for query and claim-check context

Details

Endpointhttps://api.vaultcrux.com/memory-core/mcp (Streamable HTTP)
First published25 Mar 2026
Last updated25 Mar 2026
Registry nameio.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.