Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VaultCrux Memory Core

REMOTE · API.VAULTCRUX.COM · SCANNED OCT 4

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

0 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 7279 tokens (~97/item across 75 items; 75 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 23% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_deploy_readiness" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 75 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the VaultCrux Memory Core MCP server?

VaultCrux Memory Core is a hosted endpoint at https://api.vaultcrux.com/memory-core/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.vaultcrux.com

# add to Claude Code
claude mcp add --transport http cuecrux-vaultcrux-memory-core 'https://api.vaultcrux.com/memory-core/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cuecrux-vaultcrux-memory-core": {
      "url": "https://api.vaultcrux.com/memory-core/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cuecrux-vaultcrux-memory-core": {
      "type": "http",
      "url": "https://api.vaultcrux.com/memory-core/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cuecrux-vaultcrux-memory-core]
url = "https://api.vaultcrux.com/memory-core/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cuecrux-vaultcrux-memory-core": {
      "type": "remote",
      "url": "https://api.vaultcrux.com/memory-core/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cuecrux-vaultcrux-memory-core --url 'https://api.vaultcrux.com/memory-core/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cuecrux-vaultcrux-memory-core:
    url: "https://api.vaultcrux.com/memory-core/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cuecrux-vaultcrux-memory-core": {
      "Transport": "http",
      "Url": "https://api.vaultcrux.com/memory-core/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cuecrux-vaultcrux-memory-core -t streamable-http -u 'https://api.vaultcrux.com/memory-core/mcp'
// mcp.json
{
  "mcpServers": {
    "cuecrux-vaultcrux-memory-core": {
      "type": "http",
      "url": "https://api.vaultcrux.com/memory-core/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 0
    • Server version: v0.3.4+sha.2591acf0119c → v0.3.4+sha.2db2250f556f functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Oct 2026 · Probed https://api.vaultcrux.com/memory-core/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.vaultcrux.com CN=YE1,O=Let's Encrypt,C=US 18 Jul 2026 16 Oct 2026 ECDSA 256 ECDSA-SHA384 5637c4bcfe812de49c2a96e68bbdf41af05
SANs: api.vaultcrux.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.vaultcrux.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
vaultcrux.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.vaultcrux.com/memory-core/mcp Verified 200
http (plaintext) http://api.vaultcrux.com/memory-core/mcp HTTPS enforced 308 https://api.vaultcrux.com/memory-core/mcp
MCP tools · 75 exposed · ~7,279 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
admit_character_kernel_entry ~109

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.

NameTypeReqDescription
agent_idstringyes–
expected_behaviorobjectyes–
expected_sufficiency_max–––
expected_sufficiency_min–––
rationalestringyes–
situation_fingerprintstringyes–
supersedes_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

answer_elicitation ~81

Submit an answer to an elicitation question. Triggers coverage re-assessment, follow-up question selection, and automatic output routing to appropriate record types (operating rhythms, constraints, decision context, operator profile). Returns the next question or session completion.

NameTypeReqDescription
answer–yes–
question_idstringyes–
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

assess_answerability ~100

Sufficiency gate — can this question be answered with current evidence? Pass your query and optionally the fact rows you have gathered. Returns: answerable (yes/no), missing fields, contradictory fields, recommended next tool, and confidence. Use this BEFORE forcing a best-guess answer. If answerable=false, it is better to say 'insufficient evidence' than to guess wrong.

NameTypeReqDescription
candidate_rowsarray––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

assess_character_drift ~67

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

NameTypeReqDescription
agent_idstringyes–
min_decision_countinteger––
window_endstring––
window_startstring––

Structured output declared, but exposes no named fields.

No examples provided.

assess_coverage ~107

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 topic, search with different terms before answering. Addresses 'do I have enough evidence to answer this?'

NameTypeReqDescription
action_typesarray––
domainsarray––
task_descriptionstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

assess_delegation_readiness ~102

Multi-dimensional delegation readiness assessment. Checks operator profile completeness, operating rhythm coverage, constraint coverage, knowledge coverage, and decision framework coverage relative to the task. Returns overall readiness signal (ready/likely_ready/needs_work/not_ready), dimension-level gaps, and prioritised recommended actions. This is the pre-flight check for delegation, not for action (that's verify_before_acting).

NameTypeReqDescription
operator_idstring––
task_descriptionstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

build_timeline ~96

Deterministic timeline constructor for temporal reasoning. Finds all dated events matching your query, normalizes dates, and returns them sorted chronologically. Use for 'what order', 'before/after', 'earliest/latest' questions. Returns unresolved events (found but no date) separately.

NameTypeReqDescription
anchor_eventstring––
as_ofstring––
querystringyes–
relationstring––

Structured output declared, but exposes no named fields.

No examples provided.

check_claim ~82

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 before answering.

NameTypeReqDescription
agent_idstring––
claim_textstringyes–
limitinteger––
NameTypeReqDescription
confidencenumberyes–
matchesarrayyes–
verdictstringyes–

No examples provided.

check_constraints ~69

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

NameTypeReqDescription
action_descriptionstringyes–
metadataobject––
target_resourcesarray––
team_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

check_deploy_readiness ~141

Is it safe to deploy these changes? Cross-references your changed modules against active constraints, recent incidents, knowledge freshness, and active alerts. Returns a composite verdict (ready/caution/block) with per-module breakdown and actionable recommendations. Use BEFORE deploying to catch constraint violations, recent regressions in the same area, stale knowledge that needs verification, and active alerts that might interact with your changes.

NameTypeReqDescription
changed_filesarray–Specific files changed (for constraint matching)
changed_modulesarrayyesModules being deployed (e.g. ['Engine', 'VaultCrux'])
deploy_targetstring–Deploy target environment (default 'production')

Structured output declared, but exposes no named fields.

No examples provided.

checkpoint_decision_state ~100

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.

NameTypeReqDescription
assumptions_in_effectarray––
decisions_so_fararray––
open_questionsarray––
session_idstringyes–
summarystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

compare_versions ~190

Temporal-ordered view of all values recorded for an (entity, predicate) pair, with the most-recent-before-as_of flagged as current. Use this when the agent sees contradictory facts ('Rachel moved to Chicago' AND 'Rachel moved to the suburbs') and needs to know which is current. Example calls: {entity:'user', predicate:'mortgage_amount'} returns every mortgage figure you've recorded, current first. {entity:'user', predicate:'family_trip_destination'} resolves the latest family-trip destination across sessions. {entity:'user', predicate:'previous_occupation'} returns the user's earlier roles when they changed jobs. Returns current_value directly plus has_multiple_versions so the caller can signal uncertainty, and may also include a cached narrative summary when FEATURE_CAUSAL_NARRATIVES is enabled.

NameTypeReqDescription
as_of_currentstring––
entitystringyes–
predicatestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

declare_available_models ~43

Declare which models are available in this session for orchestration routing. Called once at session start.

NameTypeReqDescription
modelsarrayyes–
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

declare_constraint ~104

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

NameTypeReqDescription
assertionstringyes–
assertion_structuredobject––
constraint_typestringyes–
evidenceobject––
expires_atstring––
review_interval_daysinteger––
scopeobject––
severitystring––
team_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

decompose_expertise ~106

Decompose a high-level task class (e.g. 'handle marketing', 'review contracts') into specific steps with knowledge requirements, judgment requirements, delegation difficulty (trivial/moderate/hard/expert_only), existing coverage, and elicitation signals. Identifies which steps can be immediately delegated, which need elicitation first, and which are genuinely expert-only.

NameTypeReqDescription
depthstring––
operator_idstring––
task_classstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

derive_from_facts ~85

Safe math and selection over a fact row set. Operations: sum, count, difference, max, min, latest, earliest. Pass the rows from enumerate_memory_facts and get a deterministic result with a computation trace. Removes arithmetic slop from totals, comparisons, and 'which is highest' questions.

NameTypeReqDescription
operationstringyes–
rowsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

dismiss_skill ~64

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

NameTypeReqDescription
notesstring–Additional notes
reasonstringyesReason for dismissal
submission_idstringyesID of the skill submission to dismiss

Structured output declared, but exposes no named fields.

No examples provided.

enumerate_memory_facts ~301

Deterministic fact-table extraction for aggregation questions and curated ESI lookups. Returns a structured row set (subject, predicate, object, date, session_id, confidence) instead of prose. Use this for 'how many', 'total', 'list all' questions — count the rows instead of hoping the LLM enumerates correctly. For curated ESI facts, pass `predicate` and optional `projectionVersionTag`; then `query` is optional and the server performs an exact predicate lookup without text search. Includes missing_dimensions to flag what might not have been found. Pass `mode: "aggregation"` (with `FEATURE_AGGREGATION_PREDICATE_EXPANSION=true` on the server) to enable: synonym expansion for pickup/return/acquire verbs, category-broadened counts from entity_categories, entity_type filters (expected_entity_types), and per-object dedup (dedup_by_object).

NameTypeReqDescription
as_ofstring––
categorystring––
dedup_by_objectboolean––
dedup_by_subject_rootboolean––
expand_synonymsboolean––
expected_entity_typesarray––
limitinteger––
modestring––
predicatestring––
predicatesarray––
projectionVersionTagstring––
querystring––
subject_matchstring––

Structured output declared, but exposes no named fields.

No examples provided.

escalate_with_context ~120

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 cannot evaluate.

NameTypeReqDescription
evidence_gatheredarray––
options_consideredarray––
questionstringyes–
reasoningstringyes–
recommended_actionstringyes–
session_idstring––
urgencystring––

Structured output declared, but exposes no named fields.

No examples provided.

expand_hit_context ~102

Session-neighborhood expansion around promising retrieval hits. When you find a relevant chunk but the specific fact (name, date, amount) is in a nearby turn, use this to fetch ±N turns from the same session. Recovers facts like 'my parents', '$6', or 'Disney+' that are near but not in the retrieved chunk.

NameTypeReqDescription
hit_idsarrayyes–
modestring––
radius_turnsinteger––

Structured output declared, but exposes no named fields.

No examples provided.

extract_facts_from_sessions ~185

Scan the tenant's seeded sessions with rule-based extractors (money, counts, dates, project-role, acquire, version-chain) and emit structured facts to the projection stream so they become queryable via enumerate_memory_facts. Use when enumerate_memory_facts returns insufficient rows for aggregation, version-chain, or money questions and you suspect the fact exists but was under-predicated at ingest. Idempotent — safe to re-run (duplicate fact_hashes skipped unless overwrite_existing=true). Profile 'comprehensive' runs all rule families; narrower profiles ('money', 'counts', 'dates', 'version_chains') target a single family. Returns facts_added + rules_matched + receipt_id. Gated by FACT_EXTRACTION_MODE on the server.

NameTypeReqDescription
extraction_profilestring––
overwrite_existingboolean––
session_idsarray––

Structured output declared, but exposes no named fields.

No examples provided.

fill_gap ~56

Fill a previously reported gap with new knowledge. Gap must have been reported by a different tenant for cross-tenant credit.

NameTypeReqDescription
contentstringyes–
evidencearrayyes–
gap_receipt_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_active_alerts ~34

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

NameTypeReqDescription
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

get_architecture_rationale ~170

Why is this module built this way? Aggregates all architectural decisions, active constraints, corrections, and skills for a domain into a coherent narrative. Use BEFORE refactoring or questioning a design choice — the answer is often 'it's that way because of compliance/performance/incident X'. Returns decisions sorted by recency, active constraints that still apply, and correction history showing what was tried and reverted.

NameTypeReqDescription
domainstringyesDomain or module to explain (e.g. 'retrieval', 'auth', 'billing', 'infra')
includearray–Which artefact types to include (default: all)
limitinteger–Max results per category (default 30)
sincestring–How far back to search (ISO datetime, default 180 days)

Structured output declared, but exposes no named fields.

No examples provided.

get_audit_trail ~42

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

NameTypeReqDescription
limitinteger––
topicstringyes–
NameTypeReqDescription
itemsarrayyes–
topicstringyes–

No examples provided.

get_causal_chain ~39

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

NameTypeReqDescription
decision_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_character_kernel ~40

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

NameTypeReqDescription
agent_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_checkpoints ~58

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.

NameTypeReqDescription
limitinteger––
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_constraints ~53

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

NameTypeReqDescription
constraint_typestring––
limitinteger––
statusstring––
team_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_contradictions ~65

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).

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
itemsarrayyes–

No examples provided.

get_correction_chain ~87

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 answering with the first value you find.

NameTypeReqDescription
decision_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_decision_context ~40

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

NameTypeReqDescription
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_decisions_on_stale_context ~36

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

NameTypeReqDescription
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_domain_changelog ~116

Cross-artefact-type changelog for specified domains since a given timestamp. Returns constraints added/updated, knowledge changes, decisions recorded, and alerts raised/resolved. Use at session start to learn what changed in your domain since your last session.

NameTypeReqDescription
domainsarrayyesDomains to check for changes
includearray–Optional filter for artefact types
limitinteger–Maximum entries to return (default 500)
sincestringyesChangelog start timestamp (max 90 days ago)

Structured output declared, but exposes no named fields.

No examples provided.

get_enrichment_status ~51

Check the status of submitted corrections (pending, corroborated, merged, retracted, expired).

NameTypeReqDescription
correction_idstring––
limitinteger––
statusstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_escalation_recommendation ~71

Get model routing recommendation for a query based on composite confidence and difficulty profile. Returns escalation advice: none, recommended, or required.

NameTypeReqDescription
current_modelstring––
querystringyes–
query_confidencenumber––
session_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_freshness_report ~75

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.

NameTypeReqDescription
limitinteger––
stale_after_daysinteger––
NameTypeReqDescription
itemsarrayyes–

No examples provided.

get_incident_context ~173

What went wrong last time we touched this module? Returns past incidents, deploy failures, gotchas, and active constraints for a module or system. Use BEFORE modifying infrastructure code, deploy scripts, or any module with a history of fragility. Surfaces the kind of tribal knowledge that prevents repeat failures — Docker bind mount traps, Vault agent write patterns, stale dist/ artifacts, port conflicts, and similar operational landmines.

NameTypeReqDescription
code_pathsarray–Specific code paths to check for related incidents
days_backinteger–How many days back to search (default 90)
limitinteger–Max results to return (default 20)
modulestringyesModule or system name (e.g. 'Engine', 'VaultCrux', 'docker', 'vault-agent')

Structured output declared, but exposes no named fields.

No examples provided.

get_knowledge_gaps ~55

List gap receipts (coverage + enumeration) for the tenant, filterable by topic and recency.

NameTypeReqDescription
gap_subtypestring––
limitinteger––
since_daysinteger––

Structured output declared, but exposes no named fields.

No examples provided.

get_my_tasks ~104

Read-through to PlanCrux task graph. Returns tasks assigned to or relevant to the calling agent, filtered by status and priority. Includes stage progress, blockers, and linked MemoryCrux artefact counts.

NameTypeReqDescription
limitinteger–Max tasks to return (default 10)
prioritystring–Filter by priority (critical, high, medium, low)
statusstring–Filter by task status (e.g. incomplete, in_progress, testing)

Structured output declared, but exposes no named fields.

No examples provided.

get_operating_rhythms ~83

Retrieve operating rhythm records for an operator — temporal behavioural patterns capturing what the human actually does (not what their calendar says). Filterable by cadence (daily, weekly, monthly) and delegation status. Returns structured sequences with delegation readiness signals.

NameTypeReqDescription
cadencestring––
delegation_statusstring––
operator_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_operator_profile ~62

Retrieve the human operator's working context: role, domain expertise, communication preferences, quality bar, trusted/distrusted sources. Returns the latest version of the profile. Defaults to the operator linked to the calling agent's passport.

NameTypeReqDescription
operator_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_passport ~70

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.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_platform_capabilities ~82

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.

NameTypeReqDescription
categorystring––
max_credit_costinteger––
min_trust_tierstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_pressure_status ~27

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

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_relevant_context ~101

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 relevant. Complements query_memory: this gives breadth, query_memory gives depth.

NameTypeReqDescription
priority_signalstring––
task_descriptionstringyes–
token_budgetintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

get_session_dossiers ~152

Retrieve pre-synthesized per-session memory dossiers (typed: experience | fact | preference; with When/Involving/To-purpose metadata). Use for multi-session or preference-style questions where stitching across conversations is the bottleneck — the dossier already summarises each session's key events. Two modes: mode='search' with a query (BM25-ish ranking over summary+purpose, optional type_filter), or mode='list' returns the tenant's most-recent dossiers chronologically. Tenants without FEATURE_SESSION_DOSSIERS enabled return an empty list (no error).

NameTypeReqDescription
limitinteger––
modestring––
querystring––
type_filterstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_signals_feed ~38

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

NameTypeReqDescription
limitinteger––
sincestring––

Structured output declared, but exposes no named fields.

No examples provided.

get_task_context ~75

Full task context: task metadata, stages with status and weight, active blockers, linked artefacts (constraints, decisions, knowledge), recent log entries, and pinned master plan version. Assembles the full picture from PlanCrux and MemoryCrux.

NameTypeReqDescription
task_idstringyesPlanCrux task ID or title

Structured output declared, but exposes no named fields.

No examples provided.

get_versioned_snapshot ~50

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

NameTypeReqDescription
limitinteger––
timestampstring––
topicstringyes–
NameTypeReqDescription
at–yes–
itemsarrayyes–
topicstringyes–

No examples provided.

Common questions

What is the VaultCrux Memory Core MCP server?

VaultCrux Memory Core is an MCP server listed in the public MCP registry as io.github.CueCrux/vaultcrux-memory-core. VaultCrux Memory Core, 32 tools: knowledge, decisions, constraints, signals, coverage. This page covers its hosted endpoint (https://api.vaultcrux.com/memory-core/mcp).

Is the VaultCrux Memory Core MCP server safe to use?

VaultCrux Memory Core scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VaultCrux Memory Core MCP server expose?

VaultCrux Memory Core exposes 75 tools: query_memory, list_topics, get_versioned_snapshot, get_audit_trail, check_claim, and 70 more. Their descriptions and schemas cost roughly 7,279 tokens of context every time the server is loaded.

Does the VaultCrux Memory Core MCP server require authentication?

No. We connected to VaultCrux Memory Core without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VaultCrux Memory Core MCP server still maintained?

VaultCrux Memory Core is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.