io.github.vdappdev2/data
NPM · @VERUSIDX/DATA-MCP
MCP server for Verus on-chain data retrieval, decryption, signing, and verification
Available components
Last scanned (20 hours ago)
Scores higher than 55% 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 177 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1969 tokens (~281/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 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
- 17 Oct 26 +1
- Stability: 0.90 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −2
- Stability: pass → 0.83 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 4 Nov 2026 · Analysed npm/@verusidx/data-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 →
decryptdata ~370
Decrypt data stored on-chain. Accepts a data descriptor (from z_listreceivedbyaddress memo), viewing key (EVK or IVK), and optional txid. With retrieve: true, the daemon fetches and decrypts the referenced data. Always pass the EVK (from z_exportviewingkey) — without it the daemon returns still-encrypted data even if the wallet holds the spending key. For encrypted identity content, pass the original encrypted DataDescriptor from signdata (not the on-chain version, which may have modified flags). Alternatively, use iddata to query and decrypt identity content by identityid and vdxfkey.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
| datadescriptor | object | – | Data descriptor object to decrypt. Typically the JSON object from z_listreceivedbyaddress memo (the value under the i4GC1YGEVD21... VDXF key). Either datadescriptor or iddata is required. |
| evk | string | – | Sapling extended full viewing key for decryption. Always pass this — export via z_exportviewingkey. Without it, data is returned still encrypted. |
| iddata | object | – | Query identity content and decrypt in one step. Alternative to datadescriptor. Returns an error if the identity has no stored content for the given parameters. Note: may fail for encrypted content st… |
| ivk | string | – | Hex incoming viewing key for decryption. |
| retrieve | boolean | – | If true, fetch the data from its on-chain reference and decrypt. Default: false. |
| txid | string | – | Transaction ID containing the data. Required when retrieve is true and the data references the same transaction. |
No output schema declared.
No examples provided.
signdata ~733
Sign data with a VerusID or transparent address. Generates a hash of the provided data and signs it. Supports multiple input modes (message, file, hex, base64, pre-computed hash, vdxfdata) and hash algorithms (sha256, sha256D, blake2b, keccak256). Can sign a single piece of data or build a Merkle Mountain Range (MMR) over multiple items. For multi-sig identities, pass an existing partial signature to accumulate signatures. Can also encrypt data to a z-address via encrypttoaddress — returns both plaintext and encrypted versions with an SSK for selective disclosure. Supports vdxfdata input — as a string (equivalent to message) or as a JSON object (VDXF binary serialization, producing a different hash). Use the object form to sign data in the same canonical format as on-chain identity contentmultimap entries. Available in read-only mode — signing does not spend funds or change blockchain/wallet state.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | VerusID name or R-address to sign with. A R-address produces a simple signature. |
| boundhashes | array | – | Array of hex hashes to bind to the signature. |
| chain | string | yes | Chain to sign on (e.g., "VRSC", "vrsctest") |
| createmmr | boolean | – | If true (or if multiple items are provided), returns MMR data and root signature. |
| datahash | string | – | Pre-computed 256-bit hex hash to sign directly. |
| encrypttoaddress | string | – | Sapling z-address to encrypt data to. Returns both encrypted and plaintext versions. The encrypted DataDescriptor can be stored on an identity via updateidentity or sent via sendcurrency. |
| filename | string | – | File path to sign. Requires -enablefileencryption daemon flag. |
| hashtype | string | – | Hash algorithm: "sha256" (default), "sha256D", "blake2b", "keccak256". |
| message | string | – | Text message to sign. |
| messagebase64 | string | – | Base64-encoded data to sign. Note: may not work in all daemon versions — prefer messagehex if base64 fails. |
| messagehex | string | – | Hex-encoded data to sign. |
| mmrdata | array | – | Array of data objects for MMR signing. Each element: {"filename" or "message" or "serializedhex" or "serializedbase64" or "vdxfdata" or "datahash": "value"}. |
| mmrhashtype | string | – | Hash type for MMR: "sha256", "sha256D", "blake2b", "keccak256". Default: "blake2b". |
| mmrsalt | array | – | Array of salt strings to protect privacy of MMR leaf nodes. |
| prefixstring | string | – | Extra string hashed during signing — must be supplied for verification. |
| signature | string | – | Existing base64 signature for multi-sig accumulation. |
| vdxfdata | – | – | VDXF-encoded structured data. String form hashes the raw string (equivalent to message). Object form performs VDXF binary serialization before hashing — use for canonical signing of VDXF-structured c… |
| vdxfkeynames | array | – | Array of VDXF key names or friendly name IDs (no i-addresses). |
| vdxfkeys | array | – | Array of VDXF keys or i-addresses to bind to the signature. |
No output schema declared.
No examples provided.
verifysignature ~338
Verify a signature produced by signdata. Checks that the signature is valid for the given data and identity/address. Returns signaturestatus: "verified" or "invalid" — always check this field. By default, validates against the identity's keys at the block height stored in the signature — use checklatest to verify against the identity's current keys instead.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | VerusID name or R-address to verify against. |
| boundhashes | array | – | Hashes bound during signing (must match). |
| chain | string | yes | Chain to verify on (e.g., "VRSC", "vrsctest") |
| checklatest | boolean | – | If true, verify against the identity's current keys. Default: false (verify against keys at the signing height stored in the signature). |
| datahash | string | – | Pre-computed 256-bit hex hash that was signed. |
| filename | string | – | File path that was signed. |
| hashtype | string | – | Hash algorithm used during signing. Default: "sha256". |
| message | string | – | Text message that was signed. |
| messagebase64 | string | – | Base64-encoded data that was signed. |
| messagehex | string | – | Hex-encoded data that was signed. |
| prefixstring | string | – | Prefix string used during signing (must match). |
| signature | string | yes | Base64-encoded signature to verify. |
| vdxfkeynames | array | – | VDXF key names bound during signing (must match). |
| vdxfkeys | array | – | VDXF keys bound during signing (must match). |
No output schema declared.
No examples provided.
z_exportviewingkey ~109
Export the extended viewing key (EVK) for a shielded address. The viewing key allows decryption of all data encrypted to this z-address without granting spending authority. Share it to grant read-only access. Pass the returned key as the evk parameter to decryptdata.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The shielded (zs-) address to export the viewing key for. |
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
No output schema declared.
No examples provided.
z_importviewingkey ~175
Import a viewing key to enable decryption of data encrypted to another z-address. Grants read-only access without spending authority. The key can be obtained from z_exportviewingkey. After import, decryptdata can decrypt data encrypted to that address without passing the key explicitly. Note: rescan can take minutes if scanning a large block range.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to import on (e.g., "VRSC", "vrsctest") |
| rescan | string | – | Whether to rescan the wallet for transactions: "yes", "no", or "whenkeyisnew" (default). |
| startHeight | number | – | Block height to start rescan from. Default: 0. |
| vkey | string | yes | The viewing key to import (from z_exportviewingkey). |
No output schema declared.
No examples provided.
z_listreceivedbyaddress ~153
List transactions and data received at a shielded (z) address. Data transactions appear with amount: 0 and a memo containing the data descriptor (a JSON object keyed by the VDXF datadescriptor address). Use this as step 1 of the data retrieval pipeline: list received data, then pass the descriptor to decryptdata. Value transactions appear with their amount and standard memo.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The shielded (zs-) address to list received transactions for. |
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
| minconf | number | – | Only include transactions confirmed at least this many times. Default: 1. |
No output schema declared.
No examples provided.
z_viewtransaction ~91
View detailed shielded transaction information including spends and outputs for a z-transaction in the wallet. Shows addresses, amounts, memos, and output indices. Useful for inspecting data-carrying transactions to understand their structure before decryption.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
| txid | string | yes | Transaction ID to inspect. |
No output schema declared.
No examples provided.
How do I install the io.github.vdappdev2/data MCP server?
io.github.vdappdev2/data runs locally as an npm package, launched with npx -y @verusidx/data-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/data-mcp
claude mcp add vdappdev2-data -- npx -y @verusidx/data-mcp
What is the io.github.vdappdev2/data MCP server?
io.github.vdappdev2/data is an MCP server listed in the public MCP registry as io.github.vdappdev2/data. MCP server for Verus on-chain data retrieval, decryption, signing, and verification. This page covers its npm package (@verusidx/data-mcp).
Is the io.github.vdappdev2/data MCP server safe to use?
io.github.vdappdev2/data scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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/data MCP server expose?
io.github.vdappdev2/data exposes 7 tools: z_listreceivedbyaddress, decryptdata, z_exportviewingkey, z_viewtransaction, signdata, and 2 more. Their descriptions and schemas cost roughly 1,969 tokens of context every time the server is loaded.
Is the io.github.vdappdev2/data MCP server still maintained?
io.github.vdappdev2/data is still listed as active in the MCP registry. We last reached this channel on 4 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/data MCP server under?
io.github.vdappdev2/data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.