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

Malware flagged

A supply-chain scanner flagged a high-severity malware risk in this package. Treat it as unsafe to install until the finding is cleared. See Supply Chain Security in the trust breakdown.

io.github.ExpertVagabond/universal-blockchain

NPM · UNIVERSAL-BLOCKCHAIN-MCP · SCANNED SEP 20

ZetaChain universal blockchain MCP server

Available components

npm · universal-blockchain-mcp 0
0 this week 0 Trust /100

Recent critical change

CVE-2021-39167 affects this package (7 Aug 2026). See the changelog before you install this server.

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 Security17
  • Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
  • Dependency health was assessed across the 400 of 926 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency22
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 io.github.ExpertVagabond/universal-blockchain MCP server?

io.github.ExpertVagabond/universal-blockchain runs locally as an npm package, launched with npx -y universal-blockchain-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 · universal-blockchain-mcp

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

  • 1 Sept 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 31 Aug 26 0
    • Security disclosure: pass → unverified ▼ 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
    • Security disclosure: unverified → pass ▲ functional
  • 24 Aug 26 0
    • Security disclosure: pass → unverified ▼ 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
  • 10 Aug 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 9 Aug 26 0
    • Security disclosure: pass → unverified ▼ 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/universal-blockchain-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed npm run install-zetachain && npm run install-foundry

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 37 findings
ID CVE Severity Vector Fix available
GHSA-345p-7cg4-v4c7 CVE-2026-25536 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8r9q-7v3j-jr4g CVE-2026-0621 high yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-7grf-83vw-6f5x CVE-2022-35915 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-88g8-f5mf-f5rj CVE-2021-46320 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-9c22-pwxw-p6hx CVE-2021-46320 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L yes
GHSA-fg47-3c2x-m2wr CVE-2021-39167 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yes
GHSA-mx2q-35m2-x2rh CVE-2023-30541 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-7q85-xj36-vmfc CVE-2026-77301 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xcpc-8h2w-3j85 CVE-2026-39244 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
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-848j-6mx2-7j84 CVE-2025-14505 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L no
GHSA-fc9h-whq2-v747 CVE-2024-48948 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-vjh7-7g9h-fjfh critical yes
GHSA-2qvq-rjwj-gvw9 CVE-2026-33916 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-2w6w-674q-4c4q CVE-2026-33937 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-3mfm-83xf-c92r CVE-2026-33938 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-442j-39wm-28r2 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-7rx3-28cr-v5wh medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-9cx6-37pm-9jff CVE-2026-33939 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xhpv-hc6g-r9c6 CVE-2026-33940 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-xjpj-3mr7-gcpf CVE-2026-33941 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/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-2mjp-6q6p-2qxm CVE-2026-1525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-35p6-xmwp-9g52 CVE-2026-6733 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-4992-7rv2-5pvq CVE-2026-1527 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N yes
GHSA-8xcm-r25x-g524 CVE-2026-16728 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-g8m3-5g58-fq7m CVE-2026-11525 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-g9mf-h72j-4rw9 CVE-2026-22036 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-m8rv-5g2x-5cg5 CVE-2026-15157 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-p88m-4jfj-68fv CVE-2026-9679 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-v3r7-h72x-cjcm CVE-2026-16729 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-v9p9-hfj2-hcw8 CVE-2026-2229 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vrm6-8vpv-qv8q CVE-2026-1526 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vxpw-j846-p89q CVE-2026-12151 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 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 6
Stale 116
No linked repository 14
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 io.github.ExpertVagabond/universal-blockchain MCP server?

io.github.ExpertVagabond/universal-blockchain is an MCP server listed in the public MCP registry as io.github.ExpertVagabond/universal-blockchain. ZetaChain universal blockchain MCP server. This page covers its npm package (universal-blockchain-mcp).

Is the io.github.ExpertVagabond/universal-blockchain MCP server still maintained?

io.github.ExpertVagabond/universal-blockchain 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 io.github.ExpertVagabond/universal-blockchain MCP server under?

io.github.ExpertVagabond/universal-blockchain declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.