Is io.github.CueCrux/vaultcrux-memory-core up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

Read at https://api.vaultcrux.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 75 tools: 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.

No change to its tools between 2026-09 and 2026-10.

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy