Should my agent depend on the MCP server io.github.CueCrux/vaultcrux-memory-core?

Verdict: allow — rich-slow-shared — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

VaultCrux Memory Core

io.github.CueCrux/vaultcrux-memory-core

VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage

— the operator's own registry description reported

Publisher io.github.CueCrux · first seen 2026-08-12 · endpoint https://api.vaultcrux.com/memory-core/mcp

allow

verdict

rich-slow-shared

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-shared — safe to depend on

Cluster rich-slow-shared · distinctiveness 0.545 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency449 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools75

vs populationhigh

capabilities1

harnessB

Trust — can it rely on it?

identityshared

servers on its host2

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_686161171408c16bdb899f7a · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

admit_character_kernel_entry answer_elicitation assess_answerability assess_character_drift assess_coverage assess_delegation_readiness build_timeline check_claim check_constraints check_deploy_readiness checkpoint_decision_state compare_versions declare_available_models declare_constraint decompose_expertise derive_from_facts dismiss_skill enumerate_memory_facts escalate_with_context expand_hit_context extract_facts_from_sessions fill_gap get_active_alerts get_architecture_rationale get_audit_trail get_causal_chain get_character_kernel get_checkpoints get_constraints get_contradictions get_correction_chain get_decision_context get_decisions_on_stale_context get_domain_changelog get_enrichment_status get_escalation_recommendation get_freshness_report get_incident_context get_knowledge_gaps get_my_tasks get_operating_rhythms get_operator_profile get_passport get_platform_capabilities get_pressure_status get_relevant_context get_session_dossiers get_signals_feed get_task_context get_versioned_snapshot investigate_question issue_passport list_external_services list_topics log_progress memory_claim_check memory_freshness_report promote_skill provision_agent_context query_memory reconstruct_knowledge_state record_decision_context register_external_service request_credentialed_call retract_skill run_elicitation session_debrief submit_correction submit_skill suggest_constraint sync_pull sync_push update_constraint update_operator_profile verify_before_acting

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	75/75	✓
has a description	75/75	✓
description is substantive	75/75	✓
parameters are typed	75/75	✓
parameters are described	17/75	17/75

75 of 75 tools graded · 75 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

v0.3.4+sha.2db2250f556f

server version vaultcrux-memory-core

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:59Z	ok_tools	200	449	2025-06-18
2026-08-12T05:34:14Z	ok_tools	200	485	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.CueCrux/vaultcrux-memory-core.svg)](https://robinsaige.com/s/io.github.CueCrux/vaultcrux-memory-core)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview