VaultCrux Memory Core
Server Details
VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 76.9% over 81 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 75 tools
Several tools have overlapping purposes: check_claim and memory_claim_check are the same function with different tiers, get_freshness_report and memory_freshness_report are duplicates, get_correction_chain and compare_versions both trace history, and investigate_question subsumes many other retrieval tools. This will cause agent misselection.
Most tools follow a verb_noun pattern (get_constraints, declare_constraint, sync_pull, etc.). Exceptions like memory_claim_check, memory_freshness_report, session_debrief, and verify_before_acting deviate but are relatively few. Overall the naming is readable and mostly predictable.
75 tools is excessive for a memory server. Many are highly niche or direct duplicates (e.g., paid/free versions of the same function). The count far exceeds typical well-scoped servers and introduces cognitive overhead without proportional value.
The server covers a wide array of memory, constraint, decision, skill, and sync operations, which is impressive. However, there are notable gaps: no direct delete or edit for memory facts (only corrections/versioning), and no bulk enumeration of all stored items. The redundancy in retrieval tools also suggests an incomplete design.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- Added
memory_claim_check - Added
memory_freshness_report - Changed
query_memory1 field changed- added
Input schema / properties / formatAdded value: +{ + "enum": [ + "raw", + "narrative" + ], + "type": "string" +}
Related MCP Connectors
VaultCrux Platform — 60 tools: retrieval, proof, intel, economy, watch, org
Shared long-term memory vault for AI agents with 20 MCP tools.
Truth-validated, SHA-512-sealed AI memory for Claude & Cursor. Free tier, OAuth, 38 tools.
Cross-device AI memory with encrypted activity capture and context handoff between AI tools
Related MCP Servers
- AlicenseBqualityFmaintenanceMemory for AI coding agents. Persistent code graph + AI architecture diagrams. 32 MCP tools3296 npm6MIT

synapse-layerofficial
AlicenseBqualityBmaintenanceMCP-native persistent memory for AI agents. Stores and retrieves encrypted memories with Trust Quotient scoring, cross-agent handover protocol, and immutable audit trail. 13 tools. Remote endpoint available.1373 PyPI13Apache 2.0- AlicenseNot gradedqualityCmaintenanceCross-tool AI memory engine providing 25 MCP tools for semantic memory, session guard, trace auditing, and proactive IDE interception, all locally without API keys.7 npm3AGPL 3.0
- AlicenseCqualityAmaintenanceProvides AI assistants with persistent memory and code intelligence across all tools and conversations. Features semantic search, knowledge graphs, decision tracking, and impact analysis with 60+ tools for universal context preservation.366,802 npm45MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.