mcp-registry/io.github.cuecrux/vaultcrux-platform · vv0.3.4+sha.a5c21792df7d
As of 2026-10-18 06:44 UTC, the Cuecrux Vaultcrux Platform MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 70% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 613.8 hours.
VaultCrux Platform — 60 tools: retrieval, proof, intel, economy, watch, org
Point your MCP client at this streamable-http endpoint: https://api.vaultcrux.com/platform/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
76 of 76 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
76 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
32 parameter(s) across 10 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
8 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~18,273 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 10 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-platform/fixes
{
"name": "action_journal_query",
"description": "Search action journal receipts with filters for time range, outcome, and tool name.\n\nPrefer `cuecrux_session` as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost class. One call per session is enough; the plan is the source of routing truth for all subsequent work. This tool remains directly callable for backward compatibility; the collapsed surface is the intended surface.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Maximum number of receipts to return."
},
"since": {
"type": "string",
"description": "ISO 8601 datetime for the start of the query window."
},
"until": {
"type": "string",
"description": "ISO 8601 datetime for the end of the query window."
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Number of receipts to skip for pagination."
},
"outcome": {
"type": "string",
"description": "Filter by outcome status."
},
"tool_name": {
"type": "string",
"description": "Filter by the name of the tool that produced the receipt."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Query Action Journal Receipts"
}{
"name": "browse_bundles",
"description": "List available credit bundles for purchase.\n\nPrefer `cuecrux_session` as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost class. One call per session is enough; the plan is the source of routing truth for all subsequent work. This tool remains directly callable for backward compatibility; the collapsed surface is the intended surface.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Maximum number of bundles to return."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Browse Bundles"
}{
"name": "create_coalition",
"description": "Create a multi-agent coalition to address a knowledge gap.\n\nPrefer `cuecrux_session` as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost class. One call per session is enough; the plan is the source of routing truth for all subsequent work. This tool remains directly callable for backward compatibility; the collapsed surface is the intended surface.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"gap_description"
],
"properties": {
"expires_at": {
"type": "string",
"description": "ISO 8601 expiry timestamp."
},
"budget_cap_crux": {
"type": "number",
"description": "Budget cap in crux credits (defaults to 10)."
},
"gap_description": {
"type": "string",
"minLength": 1,
"description": "Description of the knowledge gap."
},
"initial_pledge_crux": {
"type": "number",
"description": "Initial pledge in crux credits (defaults to 1)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create Coalition"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.cuecrux/vaultcrux-platform"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.cuecrux/vaultcrux-platform"}) over MCP.
cuecrux_session ~662 tokensmemory_reason_about ~466 tokensmemory_retrieve ~421 tokensdeclare_revenue_willingness ~418 tokensquery_vault ~369 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-platform?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-platform?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-platform.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-platform.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-platform?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:62d0d61ad1852c82…, first seen 2026-10-17, included at leaf 12539 of 33,972. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable data servers · most reliable knowledge servers · most reliable finance servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 06:44 UTC, the Cuecrux Vaultcrux Platform MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 70% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 613.8 hours.
Cuecrux Vaultcrux Platform MCP server advertises 76 tools, including accept_handoff_package, action_journal_query, annotate_session, browse_bundles, change_seat_role.
Point your MCP client at this streamable-http endpoint: https://api.vaultcrux.com/platform/mcp
Glimind scanned all 76 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.