VaultCrux Memory Core

Last 30 days

Uptime

100%

Response time

260 ms typical, 260 ms slowest 5%

Last check

6 h ago

Next check

any minute now

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "vaultcrux-memory-core": {
      "type": "http",
      "url": "https://api.vaultcrux.com/memory-core/mcp"
    }
  }
}

75 tools

• query_memory

  Search the user's conversation memory. Returns ranked results with content, source timestamps, and confidence scores. For KNOWLEDGE UPDATE questions ('current', 'now', 'most recent'): make two calls — one with scoring_profile='balanced' and one with scoring_profile='recency' — th

• list_topics

  List VaultCrux Memory Core topic groups with freshness metadata.

• get_versioned_snapshot

  Get the latest versioned snapshot for a VaultCrux Memory Core topic at an optional timestamp.

• get_audit_trail

  Read VaultCrux Memory Core import audit history and linked receipt hashes for a topic.

• check_claim

  Verify a proposed answer against memory before committing to it. Pass your candidate answer as claim_text. Returns supporting and contradicting evidence with confidence scores. Use as a pre-answer gate: if contradicting evidence exists or support is weak, investigate further befo

• memory_claim_check

  agent-ux-04 paid-tier source-linked claim check. Same upstream API as check_claim, plus three additional gates: (1) token_budget is REQUIRED — caps total response size by per-match token estimate (QC.2); (2) reserved-prefix topics (__agent::*, __ops::*, __bootstrap__::*) are stri

• get_freshness_report

  Check how recent the stored knowledge is across topics. Returns staleness indicators per topic. Use this when answering time-sensitive questions to verify your evidence isn't outdated. Topics with stale data may have been superseded by newer conversations not yet retrieved.

• memory_freshness_report

  Aligned with the Crux free-tier `memory_freshness` surface. Same backend as get_freshness_report with a token_budget knob (QC.2). Gated by FEATURE_MEMORY_FRESHNESS_REPORT=1.

• get_contradictions

  Find conflicting information across the user's memory. Returns groups of artefacts that contradict each other on the same topic. Use after gathering evidence for an answer — if your evidence sources disagree, this reveals which version is correct (typically the most recent).

• get_decision_context

  Retrieve agent session decisions from the CoreCrux Decision Plane, including decision IDs, outcomes, and cursor positions.

• get_causal_chain

  Get the causal chain graph for a specific decision, showing how decisions, actions, and supersessions relate.

• reconstruct_knowledge_state

  Reconstruct what the system knew at a specific point in time. Returns both current and superseded artefacts as of that timestamp. Use for temporal reasoning: 'what was true in January?' vs 'what is true now?' Compare two calls at different timestamps to see what changed.

• get_correction_chain

  Trace how a fact or decision evolved over time. When you find a value (e.g. 'Rachel moved to Chicago'), call this to check if a more recent session supersedes it. Returns the full version chain with timestamps. ALWAYS use for 'current', 'now', 'most recent' questions before answe

• get_decisions_on_stale_context

  Find decisions in a session that may have been made on stale memory context.

• record_decision_context

  Record a decision context event in the CoreCrux Decision Plane. This is a mutation operation.

• get_pressure_status

  Get Engine knowledge pressure status for the tenant — indicates whether knowledge bases are under update pressure.

• get_active_alerts

  Get active watch alerts across all watches for the tenant from the last 7 days.

• get_signals_feed

  Get the signals feed for the tenant from the WebCrux platform.

• declare_constraint

  Declare an organisational constraint (boundary, relationship, policy, or context flag) that agents must respect. This is a mutation operation.

• update_constraint

  Update an existing constraint. Content changes create a new version (append-only). Status-only changes update in place. This is a mutation operation.

• get_constraints

  List active organisational constraints, optionally filtered by type, status, or team.

• check_constraints

  Check an action against all active constraints. Returns matched constraints, match types (structural/semantic), and a combined verdict (pass/warn/block).

• verify_before_acting

  Pre-action and pre-conclusion verification gate. Checks Shield policy, org constraints, watch alerts, knowledge pressure, and memory freshness. Returns a combined verdict: proceed, warn, require_approval, or block. Use before committing to an answer when the stakes are high or wh

• suggest_constraint

  Propose an organisational constraint discovered during work for human review. Agents can suggest boundaries, policies, or context flags they discover — humans decide whether to promote them to active constraints. Low barrier (1 credit); authority gate is on promotion, not suggest

• checkpoint_decision_state

  Create a receipted snapshot of your current decision state during a long-running session. Records decisions made, assumptions in effect, and open questions. Enables resumption by the same or different agent from the last checkpoint rather than replaying from zero.

• get_checkpoints

  Retrieve decision checkpoints for a session. Returns the linked list of checkpoints in reverse chronological order. Use this to resume work from a prior checkpoint after session failure or handoff.

• assess_coverage

  Question-scoped readiness check. Given a task description, returns what the system knows and doesn't know: artefact counts by domain, freshness stats, and knowledge gaps. Use BEFORE answering to decide if you should search more or commit. If coverage is thin on the question's top

• get_relevant_context

  Task-scoped context briefing. Returns a prioritised context payload shaped by your task description, ranked by risk-if-missed. Constraints and alerts rank above general knowledge. Use at the START of reasoning about a question to get the system's best assessment of what's relevan

• escalate_with_context

  Contextual escalation — packages your full reasoning state (evidence gathered, options considered, recommended action) and routes to a human for review. Preserves work so the human responds with full context, not from scratch. Use when you hit genuine uncertainty that the system

• get_platform_capabilities

  Machine-queryable manifest of all available MemoryCrux tools, required trust tiers, and credit costs. Returns structured data for agent-to-service evaluation without reading documentation. Free (0 credits) at all tiers — discovery drives adoption.

• admit_character_kernel_entry

  Privileged curation tool for MemoryCrux v2.4 AgentCharacterKernel. Adds or supersedes an invariant expected behaviour tuple for an agent; operator-class API credentials are required by the API.

• get_character_kernel

  Return active AgentCharacterKernel entries for an agent, including expected behaviour tuples and sufficiency bands used by drift checks.

• assess_character_drift

  Run the on-demand AgentCharacterKernel distribution-layer sweep for an agent and return emitted drift events for the requested window.

• issue_passport

  Issue an agent passport with identity, sponsor lineage, and a 5-tier reputation system. Stored as a BLAKE3-hashed fact. Tiers: unverified (0), basic (10+ receipts), established (100+), trusted (500+), elite (2000+). Required before sync operations. Idempotent: calling twice retur

• get_passport

  Return the calling agent's passport with current reputation tier and receipt count. Recalculates receipt count on every call and auto-upgrades the tier when new thresholds are met (basic 10+, established 100+, trusted 500+, elite 2000+). Includes a hint for the next tier upgrade.

• sync_pull

  Pull enriched facts from a remote memory instance into the local fact store. Uses cursor-based pagination and resumes from the last pull cursor. Pulled facts carry a sync:source_receipt so they are never pushed back. Requires an agent passport with at least basic tier (10+ receip

• sync_push

  Push local facts to a remote memory instance. Private facts and sensitive entity prefixes (finance:, health:, credentials:, etc.) are never pushed. Call without confirm=true for a preview. Requires established passport tier (100+ receipts).

• submit_skill

  Submit a procedural workflow skill discovered during work. Pro+ private skills auto-approve; Starter skills enter a review queue. ATAM injection scanning runs automatically — quarantined skills cannot be promoted. Returns submission ID, approval status, and scan results.

• promote_skill

  Promote a reviewed skill submission to Engine artifacts, making it retrievable via get_relevant_context. Only pending_review skills can be promoted. Returns the promoted artifact ID.

• dismiss_skill

  Dismiss a pending or quarantined skill submission. The skill is marked as dismissed and will not be promoted.

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks