MCP server for Verus addresses — generate, validate, list transparent and shielded addresses
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"verusidx-chain": {
"args": [
"-y",
"@verusidx/chain-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
7 MCP servers giving AI agents direct, local access to the Verus blockchain — 49 tools, zero cloud dependencies. No API keys. No accounts. No intermediary between the agent and the chain.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'pnpm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config
## Summary `pnpm` accepts package names from the env lockfile `configDependencies` section and uses those names directly when creating config dependency symlinks under `node_modules/.pnpm-config`. A malicious repository can commit a crafted `pnpm-lock.yaml` whose env-lockfile document contains a traversal-shaped config dependency name such as `../../PWNED_CFGDEP`. During `pnpm install`, pnpm installs the config dependency and creates a symlink at a path derived from that name. In local testin
pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config
## Summary `pnpm` accepts package names from the env lockfile `configDependencies` section and uses those names directly when creating config dependency symlinks under `node_modules/.pnpm-config`. A malicious repository can commit a crafted `pnpm-lock.yaml` whose env-lockfile document contains a traversal-shaped config dependency name such as `../../PWNED_CFGDEP`. During `pnpm install`, pnpm installs the config dependency and creates a symlink at a path derived from that name. In local testin
pnpm: `patch-remove` could delete project-selected files outside the patches directory
## Summary The `patch-remove` deletion-scope issue tracked as GHSA-72r4-9c5j-mj57 / CAND-PNPM-030 has been addressed in pnpm. A crafted patch entry could resolve outside the configured patches directory and cause `pnpm patch-remove` to delete an arbitrary reachable file. This patch validates the configured directory and every resolved target before unlinking anything, then deletes the final directory entry without following it. ## Security boundary - Traversal and absolute paths that resolve
pnpm: `patch-remove` could delete project-selected files outside the patches directory
## Summary The `patch-remove` deletion-scope issue tracked as GHSA-72r4-9c5j-mj57 / CAND-PNPM-030 has been addressed in pnpm. A crafted patch entry could resolve outside the configured patches directory and cause `pnpm patch-remove` to delete an arbitrary reachable file. This patch validates the configured directory and every resolved target before unlinking anything, then deletes the final directory entry without following it. ## Security boundary - Traversal and absolute paths that resolve
pnpm: Hoisted install imports lockfile alias outside node_modules
## Summary The hoisted dependency alias issue tracked as GHSA-fr4h-3cph-29xv / CAND-PNPM-059 has been addressed in both pnpm and pacquet. A crafted lockfile alias could be joined directly under a hoisted `node_modules` directory. Traversal aliases could escape that directory, while reserved aliases such as `.bin` or `.pnpm` could overwrite pnpm-owned layout. This patch validates package-name semantics and path containment before graph insertion or filesystem work. ## Security boundary - The
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
MCP server for letmepost.dev. Publish across 8 social platforms from any agent.
MCP Security Weekly
Get CVE alerts and security updates for io.github.vdappdev2/address and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
7 MCP servers giving AI agents direct, local access to the Verus blockchain — 49 tools, zero cloud dependencies. No API keys. No accounts. No intermediary between the agent and the chain.
Works with Claude Code, Cursor, and any MCP-compatible client.
Prerequisites: a running Verus daemon and Node.js 18+.
Add the foundation server to your MCP client config:
{
"mcpServers": {
"verusidx-chain": {
"command": "npx",
"args": ["-y", "@verusidx/chain-mcp"]
}
}
}
Then tell your AI to call refresh_chains — it discovers your local daemons automatically. That's it.
No separate install step — npx fetches and runs the package on demand. Add more servers as you need them (see below).
| Package | Tools | Purpose |
|---|---|---|
@verusidx/chain-mcp | 11 | Foundation — chain discovery, daemon management, health checks, currency lookup, raw transactions, RPC help |
@verusidx/identity-mcp | 11 | Create, manage, and query VerusIDs |
@verusidx/send-mcp | 8 | Send, convert, and transfer currency; check balances and conversions |
@verusidx/data-mcp | 7 | Retrieve, decrypt, sign, and verify on-chain data; manage viewing keys |
@verusidx/address-mcp | 6 | Generate, validate, and list transparent and shielded addresses |
@verusidx/marketplace-mcp | 5 | On-chain offers and trades |
@verusidx/definecurrency-mcp | 1 | Define and launch new currencies |
chain-mcp is the foundation. It discovers running daemons and writes a registry file that all other servers read. Install it first. Every tool requires a chain parameter (e.g., "VRSC", "vrsctest") — there is no default chain.
Each server is independent — add or remove without affecting the others:
{
"mcpServers": {
"verusidx-chain": {
"command": "npx",
"args": ["-y
... [View full README on GitHub](https://github.com/vdappdev2/verusidx-mcp#readme)