VaultCrux Memory Core

io.github.CueCruxPublished by GitHub account CueCruxv0.2.0Updated Oct 24, 2026

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

The publisher's own server: core.blue

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Connects an assistant to a hosted VaultCrux memory service with 32 tools for knowledge, decisions, constraints, signals and coverage.

What you can do
VaultCrux Memory Core is a remote MCP server exposing 32 tools grouped around knowledge, decisions, constraints, signals and coverage. It lets an assistant query stored memory and run claim checks, with an optional agent id header to override the query and claim-check context. Reads are scoped to a tenant. The manifest does not list individual tool names or descriptions.
When to use it
Worth adding when an assistant should draw on a shared, tenant-scoped memory of knowledge, decisions and constraints rather than only its own context. Useful for teams that already keep records in VaultCrux and want an assistant to query them or verify claims against them. Less suitable if you have no VaultCrux tenant or API key.
Requirements
A remote MCP endpoint at over streamable HTTP. Authentication uses custom headers: x-api-key (required secret), x-tenant-id (required) and x-agent-id (optional). No packages or environment variables are declared. Network access to the endpoint is needed.
Before you install
The server is a remote endpoint, so queries and claim checks are sent to api.vaultcrux.com. It requires a secret API key (x-api-key) plus x-tenant-id and an optional x-agent-id header; treat the key as sensitive and avoid exposing it in shared configuration. The description mentions claim-check and coverage tools, but no tool list is published, so confirm what the tools read or change before relying on them.

Installation

In SourceWeft

  1. Open VaultCrux Memory Core in the dashboard and add it to a workspace.
  2. Connect Custom headers credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.CueCrux%2Fvaultcrux-memory-core/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vaultcrux-memory-core": {
      "type": "http",
      "url": "https://api.vaultcrux.com/memory-core/mcp",
      "headers": {
        "x-api-key": "<VALUE>",
        "x-tenant-id": "<VALUE>",
        "x-agent-id": "<VALUE>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Core integrations

core.blue

blue.coreOfficial publisher

Remote MCP endpoint for core.blue's private per-customer agent memory "houses": read its manual, try a sandbox, get pricing and recommendations, and request a…

Streamable HTTPWeb executable
Knowledge & Memory10 toolsNov 4, 2026

Untyped Plutus Core Mcp

Published by GitHub account mrfentmen

A local stdio MCP server for Untyped Plutus Core that lets an assistant read, check, lint, scaffold and run code.

STDIODesktop only
Developer ToolsNot validated yetNov 8, 2026

Brevio Core

Published by GitHub account Brevio-Ventures

Local code-rule scanner for coding agents: scan diffs or files, explain rules, apply safe fixes, and turn a fix into a guard, with no model call.

STDIODesktop only
Developer Tools11 toolsNov 8, 2026

brain-core

Published by GitHub account xy-claude

Local MCP server that gives a Claude Code agent persistent memory across sessions, stored as markdown files plus a SQLite and vector index on your disk.

STDIODesktop only
Files & StorageNot validated · the package did not installNov 7, 2026

Scovant Core

Published by GitHub account Scovant

Passive AI-agent readiness scan of a website: robots, llms.txt, JSON-LD, MCP discovery, security.

STDIODesktop only
AI & MLNot validated yetNov 3, 2026