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.

VaultPilot MCP

NPM · VAULTPILOT-MCP · SCANNED SEP 20

Self-custodial crypto + DeFi MCP for AI agents. Ledger-signed. EVM, TRON, Solana, BTC, LTC.

Available components

npm · vaultpilot-mcp 42
−4 this week 42 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security83
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects toml 3.0.0, reached via @kamino-finance/klend-sdk > @coral-xyz/anchor > toml. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 738 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency87
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to szhygulin/vaultpilot-mcp). View diagnostics → Pass
  • License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 137 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the VaultPilot MCP server?

VaultPilot MCP runs locally as an npm package, launched with npx -y vaultpilot-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · vaultpilot-mcp

# add to Claude Code
claude mcp add szhygulin-vaultpilot-mcp -- npx -y vaultpilot-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "szhygulin-vaultpilot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vaultpilot-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "szhygulin-vaultpilot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vaultpilot-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add szhygulin-vaultpilot-mcp -- npx -y vaultpilot-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "szhygulin-vaultpilot-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "vaultpilot-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add szhygulin-vaultpilot-mcp --command npx --arg -y --arg vaultpilot-mcp
# ~/.hermes/config.yaml
mcp_servers:
  szhygulin-vaultpilot-mcp:
    command: "npx"
    args: ["-y", "vaultpilot-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "szhygulin-vaultpilot-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "vaultpilot-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add szhygulin-vaultpilot-mcp -t stdio -c npx -a -y vaultpilot-mcp
// mcp.json
{
  "mcpServers": {
    "szhygulin-vaultpilot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vaultpilot-mcp"
      ]
    }
  }
}
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.

  • 18 Sept 26 −4
    • Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan. security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess. functional
  • 9 Sept 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 8 Sept 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 4 Sept 26 0
    • CVE-2026-63376 affects this package: high ▼ security
    • CVE-2026-71429 affects this package: high ▼ security
    • CVE-2026-77465 affects this package: high ▼ security
    • Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan. security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess. functional
  • 28 Aug 26 +4
    • Stability: Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change. security
    • Tool safety: Tool safety not yet verified: the captured tool definitions were too large for us to store in full, and the trim removes the very descriptions this category reads. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy. functional
    • Schema quality: Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy. 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
  • 12 Aug 26 0
    • Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess. functional
  • 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
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 20 Sept 2026 · Analysed npm/vaultpilot-mcp@0.14.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo szhygulin/vaultpilot-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/szhygulin/vaultpilot-mcp/.github/workflows/publish.yml@refs/tags/v0.14.4
Rekor log index 1442220954
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:8f7ca799ec579e3f9ab4cd7cec353203037565c4376ec610721ceec5ba3ca30caa7a66a54c6b0c095af3cc14558d8fae0729715ec6d8df80cc31603bb

Background: How many MCP packages publish verified provenance →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-3gc7-fjrx-p6mg CVE-2025-3194 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-82x6-q7mm-w9cf CVE-2026-77465 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v5mp-jgw5-2x6j CVE-2026-63376 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 5
Stale 98
No linked repository 11
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the VaultPilot MCP server?

VaultPilot MCP is listed in the public MCP registry as io.github.szhygulin/vaultpilot-mcp. Self-custodial crypto + DeFi MCP for AI agents. Ledger-signed. EVM, TRON, Solana, BTC, LTC. This page covers its npm package (vaultpilot-mcp).

Is the VaultPilot MCP server safe to use?

VaultPilot MCP scores 42 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

Is the VaultPilot MCP server still maintained?

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

What licence is the VaultPilot MCP server under?

VaultPilot MCP declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.