Other · Remote MCP server
VaultCrux Platform
VaultCrux Platform - 60 tools: retrieval, proof, intel, economy, watch, org.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.CueCrux/vaultcrux-platform- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-03-26
- Updated
- 2026-03-26
- Publisher
- CueCrux (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/CueCrux) · how
- Repository
- github.com/CueCrux/VaultCrux
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.vaultcrux.com/platform/mcp | x-api-key (required, secret), x-tenant-id (required), x-agent-id |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect VaultCrux Platform
VaultCrux Platform is a remote MCP server: there is nothing to install. Its endpoint is https://api.vaultcrux.com/platform/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares HTTP headers for the connection: x-api-key (required, secret), x-tenant-id (required) and x-agent-id. A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from CueCrux (GitHub)
| Server | Runs |
|---|---|
| VaultCrux Memory CoreVaultCrux Memory Core - 32 tools: knowledge, decisions, constraints, signals, coverage. | Remote · HTTPLive check: ✓ handshake |
More other servers
| Server | Runs |
|---|---|
| Variel MCP ServerGenerate your brand in-agent, then keep tokens, components, and copy on-brand over MCP. | Local · stdio |
| Vastu Shastra MCP Server by RoxyAPIVastu entrance padas, the 81 pada mandala, plot and room analysis, Ayadi and griha pravesh timing. | Remote · HTTPLive check: ✓ handshake |
| Vault Health MCPObsidian vault structural health: broken links, orphans, missing frontmatter, safe auto-repair. | Local · stdio |
| Vault MCPMCP server for credential isolation - bots use passwords and API keys without seeing them. | Local · stdio |
| vaultgateSelf-hosted remote MCP server for Bitwarden and Vaultwarden with OAuth 2.1; agents hold tokens only. | Remote · HTTP |
| vaultguardAI agents use your Obsidian secrets by name - values never reach their context. | Local · stdio |
| Vcp MCPValue Context Protocol tools: VCP/I tokens, CSM1 codes, VCP-Lite, and context encoding. | Local · stdio |
| VDatum MCP ServerMCP server for vertical datum conversions using coastalmodeling-vdatum. | Local · stdio |