VaultCrux Platform
Wire your agent into the full VaultCrux Platform—60 MCP tools for retrieval, proof, intel, economy, watch, and org—when Memory Core alone is not enough.
Overview
VaultCrux Platform is a Build-phase MCP server that exposes 60 tools for retrieval, proof, intel, economy, watch, and org through VaultCrux’s hosted API.
What is this MCP server?
- 60 MCP tools across retrieval, proof, intel, economy, watch, and org
- Remote streamable-http MCP at api.vaultcrux.com/platform/mcp
- Auth via x-api-key and required x-tenant-id; optional x-agent-id override
- VaultCrux Platform server version 0.1.0 from shared CueCrux/VaultCrux repository
- Complements VaultCrux Memory Core for expanded agent governance and operations
- 60 MCP tools across six capability areas in server description
- Endpoint: api.vaultcrux.com/platform/mcp
What problem does it solve?
Scaling agent features means stitching many VaultCrux APIs by hand, which slows shipping and fragments auth and tenant handling.
Who is it for?
Builders deploying VaultCrux-backed agents that need platform-wide retrieval, proof, intel, economy, watch, and org tools in one MCP.
Skip if: Hackathon prototypes with no VaultCrux tenant, or users who only need the 32-tool Memory Core slice.
What do I get? / Deliverables
After registration, your agent can call sixty platform MCP tools over one streamable-http endpoint with consistent VaultCrux headers.
- Single remote MCP registration to VaultCrux Platform
- Agent access to 60 tools across retrieval, proof, intel, economy, watch, and org
Recommended MCP Servers
Journey fit
Platform-wide VaultCrux capabilities are integrated during Build as you connect agents to retrieval, governance, and org-scoped services. Integrations fits because this MCP is the broad HTTP bridge to VaultCrux platform APIs beyond a single memory slice.
How it compares
Full VaultCrux platform MCP (60 tools), not Memory Core-only memory or a self-hosted open-source agent framework.
Common Questions / FAQ
Who is VaultCrux Platform for?
Solo builders and small teams standardizing on VaultCrux who want their coding agents to reach retrieval, proof, intel, economy, watch, and org APIs via MCP.
When should I use VaultCrux Platform?
Use it during Build when integrating agent features that span multiple VaultCrux domains and you prefer one MCP catalog over custom REST clients.
How do I add VaultCrux Platform to my agent?
Point your MCP client at https://api.vaultcrux.com/platform/mcp with streamable-http transport and configure x-api-key, x-tenant-id, and optional x-agent-id headers.