Skip to content
MCP Server Directory logo
developer-tools

Coin_daemon_mcp

MCP server for interacting with cryptocurrency daemon RPC interfaces (BETA)

Reviewed overview

MCP サーバー概要

What is Coin_daemon_mcp? Coin_daemon_mcp is a Model Context Protocol (MCP) server (BETA) that exposes cryptocurrency daemon RPC interfaces to AI assistants, enabling controlled management and interaction with crypto nodes (send transactions, query balances, run RPC commands, etc.).

How to use it

  • Install: npm install @raw391/coin-daemon-mcp or install via Smithery (npx @smithery/cli install @raw391/coin_daemon_mcp --client claude).
  • Configure Claude Desktop by adding an MCP server entry that runs the package (set CONFIG_PATH to your config.json).
  • Create a config.json describing one or more daemons (coinName, nickname, rpcEndpoint, rpcUser, rpcPassword).
  • Ensure daemon RPC is enabled and configured (server=1, rpcuser, rpcpassword, rpcallowip=127.0.0.1).
  • Start/restart Claude Desktop; the MCP will present tools, resources, and prompts for interacting with daemons.

Key features

  • Tools: send-coins, zsend-coins, shield-coins, get-balance, execute-command, check-status.
  • Resources: documentation endpoints (crypto://{coinType}/help, daemon://{name}/help) and transaction history (daemon://{name}/transactions).
  • Prompts/templates: guided transaction prompts, balance-analysis, daemon-diagnostic.
  • Integration-ready: designed to plug into Claude Desktop via MCP; supports multiple daemons and optional filesystem MCP for data.

Use cases

  1. Safely sending and constructing transactions (transparent and shielded for privacy coins).
  2. Monitoring daemon health, synchronization and status checks.
  3. Querying balances and transaction history across nodes.
  4. Guided wallet management and balance analysis with AI assistance.
  5. Development and testing on testnets or limited-fund wallets for automation/AI workflows.

Security & safety (critical)

  • This server grants powerful capabilities (send txns, access wallet data, execute RPC). Use separate wallets with minimal funds, restrict RPC permissions, run on localhost, monitor interactions, and perform security audits.
  • The project is BETA — use at your own risk.

FAQ

  • Is it safe to connect my main wallet?

No. Use dedicated wallets with limited funds and follow recommended RPC/file security practices.

  • Which daemons are supported?

Any daemon with a JSON-RPC interface configurable via the provided config (examples include Zcash and Bitcoin). Custom coins supported if RPC endpoints match.

  • How do I add multiple coins/nodes?

Add multiple entries in the “daemons” array in the config.json with distinct nicknames and RPC credentials.

  • Is this production-ready?

No. The project is BETA and includes explicit security warnings; perform thorough testing and audits before using with valuable funds.

  • Where to get help or report issues?

Use the project’s GitHub Issues and Discussions; security reports via the provided security contact. License: MIT with cryptocurrency operations disclaimer.