
VaultCrux Platform
io.github.CueCruxPublished by GitHub account CueCruxv0.1.0Updated Oct 24, 2026
VaultCrux Platform — 60 tools: retrieval, proof, intel, economy, watch, org
Overview
A remote MCP endpoint exposing VaultCrux Platform's 60 tools across retrieval, proof, intel, economy, watch and org areas.
- What you can do
- VaultCrux Platform is a hosted MCP server reached over streamable HTTP at a fixed remote endpoint. The registry description lists 60 tools grouped into six areas: retrieval, proof, intel, economy, watch and org. No individual tool names or descriptions are published, so the exact actions each tool performs are not documented here.
- When to use it
- Consider it when you want an assistant to work with VaultCrux Platform capabilities such as retrieval, proof, intel, economy, watch or org functions through a hosted endpoint rather than a local package. Because the tool list is unpublished, check the provider's own documentation before relying on specific tools.
- Requirements
- A remote MCP client connecting to the VaultCrux endpoint over streamable HTTP. Authentication is required via custom headers: x-api-key (the API key secret), x-tenant-id (tenant id), and optionally x-agent-id to override the agent id. No local runtime, packages or environment variables are declared.
Installation
In SourceWeft
- Open VaultCrux Platform in the dashboard and add it to a workspace.
- Connect Custom headers credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.CueCrux%2Fvaultcrux-platform/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"vaultcrux-platform": {
"type": "http",
"url": "https://api.vaultcrux.com/platform/mcp",
"headers": {
"x-api-key": "<VALUE>",
"x-tenant-id": "<VALUE>",
"x-agent-id": "<VALUE>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
35% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.