io.github.vdappdev2/address
NPM · @VERUSIDX/ADDRESS-MCP · SCANNED AUG 3
MCP server for Verus addresses — generate, validate, list transparent and shielded addresses
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. 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 84 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @verusidx/address-mcp
claude mcp add vdappdev2-address -- npx -y @verusidx/address-mcp
codex mcp add vdappdev2-address -- npx -y @verusidx/address-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vdappdev2-address": {
"type": "local",
"command": [
"npx",
"-y",
"@verusidx/address-mcp"
],
"enabled": true
}
}
} openclaw mcp add vdappdev2-address --command npx --arg -y --arg @verusidx/address-mcp
mcp_servers:
vdappdev2-address:
command: "npx"
args: ["-y", "@verusidx/address-mcp"] {
"mcpServers": {
"vdappdev2-address": {
"command": "npx",
"args": [
"-y",
"@verusidx/address-mcp"
]
}
}
} 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.
- 3 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +31
- Malware scan: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@verusidx/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 96 packages
96 packages in the resolved dependency tree · 96 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.