VaultCrux Memory Core
REMOTE · API.VAULTCRUX.COM · SCANNED OCT 4
VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 75 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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
claude mcp add --transport http cuecrux-vaultcrux-memory-core 'https://api.vaultcrux.com/memory-core/mcp'
{
"mcpServers": {
"cuecrux-vaultcrux-memory-core": {
"url": "https://api.vaultcrux.com/memory-core/mcp"
}
}
} {
"servers": {
"cuecrux-vaultcrux-memory-core": {
"type": "http",
"url": "https://api.vaultcrux.com/memory-core/mcp"
}
}
} [mcp_servers.cuecrux-vaultcrux-memory-core] url = "https://api.vaultcrux.com/memory-core/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cuecrux-vaultcrux-memory-core": {
"type": "remote",
"url": "https://api.vaultcrux.com/memory-core/mcp",
"enabled": true
}
}
} openclaw mcp add cuecrux-vaultcrux-memory-core --url 'https://api.vaultcrux.com/memory-core/mcp' --transport streamable-http
mcp_servers:
cuecrux-vaultcrux-memory-core:
url: "https://api.vaultcrux.com/memory-core/mcp" {
"McpServers": {
"cuecrux-vaultcrux-memory-core": {
"Transport": "http",
"Url": "https://api.vaultcrux.com/memory-core/mcp"
}
}
} assistant mcp add cuecrux-vaultcrux-memory-core -t streamable-http -u 'https://api.vaultcrux.com/memory-core/mcp'
{
"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.
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
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 |
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 →
investigate_question 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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| question_date | string | – | – |
| scoring_profile | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
issue_passport 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.
| Name | Type | Req | Description |
|---|---|---|---|
| sponsor_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_external_services 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.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by service status |
Structured output declared, but exposes no named fields.
No examples provided.
list_topics List Topics ~27
List VaultCrux Memory Core topic groups with freshness metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No examples provided.
log_progress 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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | Evidence references for the log entry |
| note | string | yes | What was done |
| stage_id | string | – | Bind this log to a specific stage |
| task_id | string | yes | PlanCrux task ID |
Structured output declared, but exposes no named fields.
No examples provided.
memory_claim_check Memory Claim Check (paid) ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| claim_text | string | yes | – |
| token_budget | integer | yes | – |
| top_k | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | yes | – |
| matches | array | yes | – |
| verdict | string | yes | – |
No examples provided.
memory_freshness_report Memory Freshness Report (paid alias) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| stale_after_days | integer | – | – |
| token_budget | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No examples provided.
promote_skill 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.
| Name | Type | Req | Description |
|---|---|---|---|
| review_notes | string | – | Notes from the reviewer |
| submission_id | string | yes | ID of the skill submission to promote |
| visibility | string | – | Override target visibility |
Structured output declared, but exposes no named fields.
No examples provided.
provision_agent_context 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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_role | string | yes | – |
| operator_id | string | – | – |
| scope | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
query_memory 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| confidence_threshold | number | – | – |
| date_from | string | – | – |
| date_range | object | – | – |
| date_to | string | – | – |
| format | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| question_date | string | – | – |
| scoring_profile | string | – | – |
| topic | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
reconstruct_knowledge_state 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.
| Name | Type | Req | Description |
|---|---|---|---|
| at_timestamp | string | – | – |
| decision_id | string | yes | – |
| include_confidence_landscape | boolean | – | – |
| include_superseded | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
record_decision_context Record Decision Context ~68
Record a decision context event in the CoreCrux Decision Plane. This is a mutation operation.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| context | object | yes | – |
| decision_id | string | yes | – |
| occurred_at | string | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
register_external_service 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.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_methods | array | – | Allowed HTTP methods (default: GET, POST) |
| allowed_paths | array | – | Allowed path patterns (default: *) |
| auth_injection | object | – | How to inject the credential into requests |
| auth_type | string | yes | Authentication type |
| base_url | string | yes | Service base URL (must be HTTPS) |
| credential_value | string | yes | The credential (encrypted immediately, never stored plaintext) |
| display_name | string | yes | Human-readable service name |
| rate_limit | object | – | Rate limits for this service |
| service_id | string | yes | Tenant-unique identifier for the service |
Structured output declared, but exposes no named fields.
No examples provided.
request_credentialed_call Credentialed External 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.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | – | Additional headers (not auth) |
| method | string | yes | HTTP method |
| path | string | yes | Request path (e.g. /v1/chat/completions) |
| payload | object | – | Request body for POST/PUT |
| service_id | string | yes | Registered service ID |
| session_id | string | – | Session ID for audit trail |
Structured output declared, but exposes no named fields.
No examples provided.
retract_skill 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.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | – | Additional notes |
| reason | string | yes | Reason for retraction |
| submission_id | string | yes | ID of the skill submission to retract |
Structured output declared, but exposes no named fields.
No examples provided.
run_elicitation 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.
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | yes | – |
| operator_id | string | – | – |
| resume_from | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
session_debrief 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.
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions_invalidated | array | – | Assumptions that were invalidated during the session |
| assumptions_validated | array | – | Assumptions that were validated during the session |
| discoveries | array | – | Discoveries made during the session |
| session_id | string | yes | Session ID for the debrief |
| suggested_actions | array | – | Actions to route from session discoveries |
Structured output declared, but exposes no named fields.
No examples provided.
submit_correction 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.
| Name | Type | Req | Description |
|---|---|---|---|
| corrected_content | string | yes | – |
| correction_type | string | yes | – |
| evidence | array | yes | – |
| original_item_id | string | yes | – |
| parent_receipt_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
submit_skill 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_role | string | – | Role of the submitting agent |
| content | string | yes | Full procedural skill content (markdown) |
| discovery_context | string | – | How/where the skill was discovered |
| run_id | string | – | AgentCrux run ID |
| session_id | string | – | Session ID for provenance tracking |
| skill_domains | array | – | Knowledge domains this skill applies to |
| skill_tool_references | array | – | Tool names this skill references |
| skill_trigger_description | string | – | When this skill should be activated |
| supersedes_artifact_id | integer | – | Artifact ID this skill replaces |
| target_visibility | string | – | Visibility scope for the skill |
| title | string | yes | Short title summarising the skill |
Structured output declared, but exposes no named fields.
No examples provided.
suggest_constraint 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.
| Name | Type | Req | Description |
|---|---|---|---|
| assertion | string | yes | – |
| confidence | number | – | – |
| constraint_type | string | yes | – |
| discovery_context | string | – | – |
| evidence | object | – | – |
| scope | object | – | – |
| session_id | string | – | – |
| severity | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sync_pull 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).
| Name | Type | Req | Description |
|---|---|---|---|
| entity_prefix | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sync_push 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).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_constraint 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.
| Name | Type | Req | Description |
|---|---|---|---|
| assertion | string | – | – |
| assertion_structured | object | – | – |
| constraint_id | string | yes | – |
| evidence | object | – | – |
| expires_at | – | – | – |
| review_interval_days | – | – | – |
| scope | object | – | – |
| severity | string | – | – |
| status | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_operator_profile 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.
| Name | Type | Req | Description |
|---|---|---|---|
| communication_preferences | object | – | – |
| distrusted_sources | array | – | – |
| domain_expertise | array | – | – |
| experience_level | string | – | – |
| operator_id | string | – | – |
| quality_bar | array | – | – |
| role_description | string | – | – |
| trusted_sources | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_before_acting 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action_description | string | yes | – |
| is_mutation | boolean | – | – |
| metadata | object | – | – |
| publisher_id | string | – | – |
| server_digest | string | – | – |
| target_resources | array | – | – |
| team_id | string | – | – |
| tool_name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.