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
investigate_question ~188

Composite server-side investigation tool. Pass a question and the server automatically: (1) detects intent (aggregation/temporal/ordering/knowledge-update/recall), (2) queries the entity index for structured facts, (3) builds a timeline for temporal questions, (4) retrieves memory chunks with the right scoring profile, (5) expands context around sparse hits, (6) derives counts/sums for aggregation, (7) assesses answerability, and (8) returns a recommendation. Use this as your FIRST tool for any non-trivial question — it does the multi-step investigation that would otherwise take 4-6 individual tool calls. The response includes structured facts, timeline, retrieved chunks, derived results, answerability assessment, and a recommendation for how to answer.

NameTypeReqDescription
questionstringyes–
question_datestring––
scoring_profilestring––

Structured output declared, but exposes no named fields.

No examples provided.

issue_passport ~92

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 returns the existing passport.

NameTypeReqDescription
sponsor_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

list_external_services ~55

List registered external services available to the calling agent. Returns service IDs, display names, allowed methods/paths, and rate limit state. Does not return credentials or credential references.

NameTypeReqDescription
statusstring–Filter by service status

Structured output declared, but exposes no named fields.

No examples provided.

list_topics ~27

List VaultCrux Memory Core topic groups with freshness metadata.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
itemsarrayyes–

No examples provided.

log_progress ~110

Receipted write-through to PlanCrux's log endpoint. Appends a structured log entry to a task with optional evidence references and stage binding. Cannot change task or stage status (human-only), but records work done, findings, and blockers encountered.

NameTypeReqDescription
evidencearray–Evidence references for the log entry
notestringyesWhat was done
stage_idstring–Bind this log to a specific stage
task_idstringyesPlanCrux task ID

Structured output declared, but exposes no named fields.

No examples provided.

memory_claim_check ~173

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 stripped from matches (T.1); (3) per-match audit_links carry an offline-verify CLI hint (`corecruxctl receipts verify <id>`) so the host IDE can render a one-click verify badge per supporting / contradicting memory. Gated by FEATURE_MEMORY_CLAIM_CHECK=1 (default off).

NameTypeReqDescription
agent_idstring––
claim_textstringyes–
token_budgetintegeryes–
top_kinteger––
NameTypeReqDescription
confidencenumberyes–
matchesarrayyes–
verdictstringyes–

No examples provided.

memory_freshness_report ~81

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.

NameTypeReqDescription
limitinteger––
stale_after_daysinteger––
token_budgetinteger––
NameTypeReqDescription
itemsarrayyes–

No examples provided.

promote_skill ~78

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.

NameTypeReqDescription
review_notesstring–Notes from the reviewer
submission_idstringyesID of the skill submission to promote
visibilitystring–Override target visibility

Structured output declared, but exposes no named fields.

No examples provided.

provision_agent_context ~107

Generate a structured, receipted context package for a new agent — the equivalent of soul.md + heartbeat.md + user.md but machine-queryable and backed by MemoryCrux records. Includes identity, operator context, active constraints, operating rhythms, knowledge briefing, and heartbeat schedule. Scope: minimal (identity + constraints), standard (all), comprehensive (standard + full knowledge).

NameTypeReqDescription
agent_rolestringyes–
operator_idstring––
scopestring––

Structured output declared, but exposes no named fields.

No examples provided.

query_memory ~208

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' — then use the value from the most recent source_timestamp. For COUNTING questions ('how many', 'total'): results may not be exhaustive — search with varied terms and enumerate explicitly before counting. If all results score below 0.3, reformulate with synonyms or specific entity names from the question.

NameTypeReqDescription
agent_idstring––
confidence_thresholdnumber––
date_fromstring––
date_rangeobject––
date_tostring––
formatstring––
limitinteger––
querystringyes–
question_datestring––
scoring_profilestring––
topicstring––
NameTypeReqDescription
resultsarrayyes–

No examples provided.

reconstruct_knowledge_state ~103

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.

NameTypeReqDescription
at_timestampstring––
decision_idstringyes–
include_confidence_landscapeboolean––
include_supersededboolean––

Structured output declared, but exposes no named fields.

No examples provided.

record_decision_context ~68

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

NameTypeReqDescription
agent_idstring––
contextobjectyes–
decision_idstringyes–
occurred_atstring––
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

register_external_service ~180

Register an external service and store its credential via Vault Transit. Human-only (admin or owner role). The credential is encrypted immediately on receipt and never stored in plaintext. Returns the service registration record without the credential.

NameTypeReqDescription
allowed_methodsarray–Allowed HTTP methods (default: GET, POST)
allowed_pathsarray–Allowed path patterns (default: *)
auth_injectionobject–How to inject the credential into requests
auth_typestringyesAuthentication type
base_urlstringyesService base URL (must be HTTPS)
credential_valuestringyesThe credential (encrypted immediately, never stored plaintext)
display_namestringyesHuman-readable service name
rate_limitobject–Rate limits for this service
service_idstringyesTenant-unique identifier for the service

Structured output declared, but exposes no named fields.

No examples provided.

request_credentialed_call ~151

Proxied external API call with server-side credential injection. VaultCrux retrieves the credential from Vault Transit, injects it per the service's auth template, makes the call, and returns the response. The credential never appears in your context window. Request and response are receipted and audit-logged.

NameTypeReqDescription
headersobject–Additional headers (not auth)
methodstringyesHTTP method
pathstringyesRequest path (e.g. /v1/chat/completions)
payloadobject–Request body for POST/PUT
service_idstringyesRegistered service ID
session_idstring–Session ID for audit trail

Structured output declared, but exposes no named fields.

No examples provided.

retract_skill ~81

Retract a previously promoted skill. Sets the Engine artifact's living status to 'retracted', removing it from future retrieval results. Use when a skill is found to be incorrect or outdated.

NameTypeReqDescription
notesstring–Additional notes
reasonstringyesReason for retraction
submission_idstringyesID of the skill submission to retract

Structured output declared, but exposes no named fields.

No examples provided.

run_elicitation ~94

Start or resume a structured elicitation session for a specific knowledge layer. Layers: operating_rhythm, recurring_decisions, dependencies, friction, judgment_patterns, quality_standards, or 'full' for all layers. Returns the first question and session metadata. Use answer_elicitation to submit answers.

NameTypeReqDescription
layerstringyes–
operator_idstring––
resume_fromstring––

Structured output declared, but exposes no named fields.

No examples provided.

session_debrief ~130

Structured session-end reflection. Routes discoveries to appropriate capture tools (suggest_constraint, submit_skill, flag_for_review). Produces a receipted debrief record. Call before closing any session longer than 10 minutes.

NameTypeReqDescription
assumptions_invalidatedarray–Assumptions that were invalidated during the session
assumptions_validatedarray–Assumptions that were validated during the session
discoveriesarray–Discoveries made during the session
session_idstringyesSession ID for the debrief
suggested_actionsarray–Actions to route from session discoveries

Structured output declared, but exposes no named fields.

No examples provided.

submit_correction ~77

Submit a correction for a knowledge item with evidence chain. The original item is never mutated — a versioned enrichment layer is created.

NameTypeReqDescription
corrected_contentstringyes–
correction_typestringyes–
evidencearrayyes–
original_item_idstringyes–
parent_receipt_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

submit_skill ~210

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.

NameTypeReqDescription
agent_rolestring–Role of the submitting agent
contentstringyesFull procedural skill content (markdown)
discovery_contextstring–How/where the skill was discovered
run_idstring–AgentCrux run ID
session_idstring–Session ID for provenance tracking
skill_domainsarray–Knowledge domains this skill applies to
skill_tool_referencesarray–Tool names this skill references
skill_trigger_descriptionstring–When this skill should be activated
supersedes_artifact_idinteger–Artifact ID this skill replaces
target_visibilitystring–Visibility scope for the skill
titlestringyesShort title summarising the skill

Structured output declared, but exposes no named fields.

No examples provided.

suggest_constraint ~117

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

NameTypeReqDescription
assertionstringyes–
confidencenumber––
constraint_typestringyes–
discovery_contextstring––
evidenceobject––
scopeobject––
session_idstring––
severitystring––

Structured output declared, but exposes no named fields.

No examples provided.

sync_pull ~73

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

NameTypeReqDescription
entity_prefixstring––

Structured output declared, but exposes no named fields.

No examples provided.

sync_push ~60

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

NameTypeReqDescription
confirmboolean––

Structured output declared, but exposes no named fields.

No examples provided.

update_constraint ~101

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

NameTypeReqDescription
assertionstring––
assertion_structuredobject––
constraint_idstringyes–
evidenceobject––
expires_at–––
review_interval_days–––
scopeobject––
severitystring––
statusstring––

Structured output declared, but exposes no named fields.

No examples provided.

update_operator_profile ~107

Update the operator profile. Creates a new version with provenance receipt (does not mutate). Accepts partial updates — fields not provided are preserved from the previous version.

NameTypeReqDescription
communication_preferencesobject––
distrusted_sourcesarray––
domain_expertisearray––
experience_levelstring––
operator_idstring––
quality_bararray––
role_descriptionstring––
trusted_sourcesarray––

Structured output declared, but exposes no named fields.

No examples provided.

verify_before_acting ~149

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 when your evidence is thin — it catches constraint conflicts and stale-context risks that query_memory alone won't surface.

NameTypeReqDescription
action_descriptionstringyes–
is_mutationboolean––
metadataobject––
publisher_idstring––
server_digeststring––
target_resourcesarray––
team_idstring––
tool_namestringyes–

Structured output declared, but exposes no named fields.

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.