io.github.vdappdev2/address
NPM · @VERUSIDX/ADDRESS-MCP
MCP server for Verus addresses — generate, validate, list transparent and shielded addresses
Available components
Last scanned (7 hours ago)
Scores higher than 62% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 178 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management97
- Stability observed for 29 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
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.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 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 5 Nov 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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Account name. Use "" (empty string) for the default account. In Verus, all addresses typically belong to the default account. |
| chain | string | yes | Chain 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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The transparent address to validate (R-address or i-address) |
| chain | string | yes | Chain 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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain 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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
| includeWatchonly | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The shielded z-address (zs1...) to validate |
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
No output schema declared.
No examples provided.
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
claude mcp add vdappdev2-address -- npx -y @verusidx/address-mcp
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 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 5 November 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.