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.

io.github.vdappdev2/address

NPM · @VERUSIDX/ADDRESS-MCP · SCANNED SEP 20

MCP server for Verus addresses — generate, validate, list transparent and shielded addresses

Available components

npm · @verusidx/address-mcp 83
0 this week 83 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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 612 tokens (~102/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 io.github.vdappdev2/address MCP server?

io.github.vdappdev2/address runs locally as an npm package, launched with npx -y @verusidx/address-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 · @verusidx/address-mcp

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

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

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/@verusidx/address-mcp@0.1.7

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 →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~612 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
getaddressesbyaccount ~111

List all transparent addresses for an account. In Verus, the default account is "" (empty string). Returns an array of R-addresses associated with the account. Use this to see all transparent addresses the wallet has generated.

NameTypeReqDescription
accountstring–Account name. Use "" (empty string) for the default account. In Verus, all addresses typically belong to the default account.
chainstringyesChain to query (e.g., "VRSC", "vrsctest")

No output schema declared.

No examples provided.

getnewaddress ~77

Generate a new transparent (R-address) for receiving payments. Use this to create fresh addresses for identity primaryaddresses, change addresses, or destination addresses. Each call generates a unique address from the wallet's keypool.

NameTypeReqDescription
chainstringyesChain to generate address on (e.g., "VRSC", "vrsctest")

No output schema declared.

No examples provided.

validateaddress ~107

Validate an address and return detailed information about it. Returns whether the address is valid, whether it belongs to this wallet (ismine), the address type, and associated metadata. Use this to verify addresses before sending funds, or to check if a given address is controlled by the local wallet.

NameTypeReqDescription
addressstringyesThe transparent address to validate (R-address or i-address)
chainstringyesChain to query (e.g., "VRSC", "vrsctest")

No output schema declared.

No examples provided.

z_getnewaddress ~74

Generate a new shielded Sapling address (zs-address) for private transactions. Use this to create addresses for identity privateaddress fields or private sends. Each call generates a unique shielded address.

NameTypeReqDescription
chainstringyesChain to generate address on (e.g., "VRSC", "vrsctest")

No output schema declared.

No examples provided.

z_listaddresses ~100

List all shielded (Sapling) addresses in the wallet. Returns an array of zs-addresses. Use this to see all shielded addresses available for private transactions, or to find an existing shielded address for use as an identity privateaddress.

NameTypeReqDescription
chainstringyesChain to query (e.g., "VRSC", "vrsctest")
includeWatchonlyboolean–Also include watchonly addresses. Default: false.

No output schema declared.

No examples provided.

z_validateaddress ~143

Validate a shielded (Sapling) z-address and return detailed information. Returns whether the address is valid, whether it belongs to this wallet (ismine), the address type, and key components (payingkey, transmissionkey, diversifier). Use this to verify z-addresses before sending funds or data, or to check if a z-address is controlled by the local wallet. Complements validateaddress, which only works for transparent (R/i) addresses.

NameTypeReqDescription
addressstringyesThe shielded z-address (zs1...) to validate
chainstringyesChain to query (e.g., "VRSC", "vrsctest")

No output schema declared.

No examples provided.

Common questions

What is the io.github.vdappdev2/address MCP server?

io.github.vdappdev2/address is an MCP server listed in the public MCP registry as io.github.vdappdev2/address. MCP server for Verus addresses, generate, validate, list transparent and shielded addresses. This page covers its npm package (@verusidx/address-mcp).

Is the io.github.vdappdev2/address MCP server safe to use?

io.github.vdappdev2/address scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.vdappdev2/address MCP server expose?

io.github.vdappdev2/address exposes 6 tools: validateaddress, z_validateaddress, getaddressesbyaccount, z_listaddresses, getnewaddress, z_getnewaddress. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.

Is the io.github.vdappdev2/address MCP server still maintained?

io.github.vdappdev2/address 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.vdappdev2/address MCP server under?

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