VaultCrux Platform
Server Details
VaultCrux Platform — 60 tools: retrieval, proof, intel, economy, watch, org
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
14 tool updates
- Added
comment_on_work - Added
create_work - Added
get_project_context - Added
github_comments_since - Added
github_open_issues - Added
github_open_prs - Added
github_recent_commits - Added
github_search - Added
list_projects - Added
list_work - Added
memory_engrams_resolve - Changed
memory_retrieve1 field changed- added
Input schema / properties / sessionProcedureHashAdded value: +{ + "description": "Hash of a session_procedure already seen by this client. When current, the server omits the procedure body.", + "type": "string" +}
- Added
memory_session_init - Added
update_work_state
6 tool updates
- Added
action_journal_query - Removed
action_journal.query - Changed
cuecrux_session3 fields changed- added
Input schema / properties / model / properties / declared / descriptionAdded value: +"Optional free-form model identifier (e.g. 'claude-haiku-4-5-20251001')." - added
Input schema / properties / model / properties / declared_family / descriptionAdded value: +"Model family. Accepts `claude|gpt|gemini|local|unknown`. If the actual family is outside this set, pick the closest match and proceed — do not skip declaring." - added
Input schema / properties / model / properties / declared_size / descriptionAdded value: +"Model size tier. Accepts `small|medium|large|frontier`. Map informal terms (e.g. 'mini'→`small`, 'flagship'→`frontier`) to the nearest enum value — do not skip declaring."
- Added
memory_reason_about - Added
memory_retrieve - Changed
query_vault1 field changed- changed
Input schema / properties / lane / descriptionPrevious value: -"Retrieval lane controlling depth and cost."New value: +"Retrieval lane controlling depth and cost. Accepts `light|verified|audit` — map informal terms (e.g. 'quick'→`light`, 'strict'→`audit`) to the nearest enum value. Defaults to `light`."
1 tool update
- Added
cuecrux_session
1 tool update
- Changed
query_vault2 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return (1-20, default 8)."New value: +"Maximum number of results to return (1-50, default 8)." - changed
Input schema / properties / limit / maximumPrevious value: -20New value: +50
60 tool updates
- First observed
accept_handoff_package - First observed
action_journal.query - First observed
annotate_session - First observed
browse_bundles - First observed
change_seat_role - First observed
create_coalition - First observed
create_handoff_package - First observed
declare_revenue_willingness - First observed
diff_receipts - First observed
explain_last_answer - First observed
find_contradictions - First observed
forecast_obsolescence - First observed
get_active_policy - First observed
get_beliefs - First observed
get_blast_radius - First observed
get_break_analysis - First observed
get_counterfactual_summary - First observed
get_credit_balance - First observed
get_credit_escrow - First observed
get_daily_briefing - First observed
get_domain_affinity - First observed
get_economy_dashboard - First observed
get_feature_requests - First observed
get_journal - First observed
get_knowledge_gaps - First observed
get_passport - First observed
get_pricing - First observed
get_proof_chunks - First observed
get_proof_receipt - First observed
get_proof_status - First observed
get_proofpack - First observed
get_reasoning_profile - First observed
get_session_context - First observed
get_spend_receipt - First observed
get_stale_pins - First observed
get_trust_level - First observed
get_watch_alerts - First observed
get_watches - First observed
invite_seat - First observed
join_coalition - First observed
list_seats - First observed
pin_receipt - First observed
proof_document - First observed
purchase_bundle - First observed
query_vault - First observed
query_with_threshold - First observed
register_agent - First observed
register_belief - First observed
request_sponsor - First observed
revoke_seat - First observed
schedule_recheck - First observed
set_policy - First observed
set_reasoning_profile - First observed
submit_feature_request - First observed
tip_agent - First observed
tip_platform - First observed
unwatch_answer - First observed
verify_passport - First observed
vote_feature_request - First observed
watch_answer
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage
Constitutional AI governance: 11 mega-tools, 13 floors, VAULT999 ledger. Human-in-loop by design.
54 AI agent tools: OSINT, intel feeds, DeFi, crypto, weather, DNS, proxies. x402 micropayments.
22 utility tools (x402 USDC on Base): currency, PDF, image, GDPR. Free health.
Related MCP Servers
- AlicenseAqualityAmaintenanceZero-Knowledge Cloud Drive for Humans and Agents. Client-side AES-256-GCM encryption with 7 MCP tools for secure file vault management — the server never sees plaintext data.72471MIT
- AlicenseNot gradedqualityDmaintenanceMethodology-transparent BTC + ETH whale forensics. 30 tools, anonymous OAuth 2.1 Free tier.MIT
- AlicenseNot gradedqualityAmaintenanceTrust-aware Nostr MCP server. 236 tools for identity, social, DMs, trust scoring, AI-to-AI dispatch, Lightning payments, privacy proofs, and encrypted vaults. NIP-46 bunker auth; keys never leave the signing device.5531MIT
- AlicenseAqualityBmaintenanceVersioned document vault system for MCP-compatible AI agents. Organizes reference knowledge (specs, contracts, rules) into per-project vaults with 36 MCP tools for inject, search, link, and version operations. Local SQLite backend. Works with Claude, Cursor, Codex, Hermes Agent. Free (3 vaults) / Pro ($9/mo).494Business Source 1.1
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Each tool has a distinct name and purpose, covering a wide range of functions. However, every description includes the same advice to prefer `cuecrux_session`, which could cause an agent to question whether to call these tools directly or rely on the session plan, slightly reducing clarity.
Tool names follow varied patterns: some use verb_noun (e.g., `create_work`), others use get_* (e.g., `get_credit_balance`), and a few are noun-based (e.g., `cuecrux_session`). While readable, the lack of a consistent convention makes the set feel less cohesive.
With 76 tools, the server surface is excessively large for typical MCP usage. The high count suggests many legacy endpoints that are intended to be superseded by a single session entry point, making the tool set feel bloated and hard to navigate.
The tool set covers a broad spectrum of capabilities including project management, work items, knowledge retrieval, cryptographic proofing, economy, GitHub integration, and agent trust. Minor gaps exist (e.g., no tool to update work item fields beyond state), but overall it is reasonably comprehensive for the platform's scope.