Sending transactions, reading wallet information, changing wallet settings and executing daemon commands are all in scope, and the README's own safety guidance is the setup instruction that matters: use a separate wallet holding limited funds, never one with real value, keep RPC scoped to localhost with strict permissions, and monitor what the assistant does. It is marked beta. The value is real — natural-language daemon operation and diagnostics — but the blast radius is your wallet.
A bridge between an assistant and one or more running cryptocurrency daemons, addressed over their RPC interfaces. Beyond tools it exposes documentation and transaction history as resources and ships prompt templates for the workflows people get wrong.
- Transparent transactions sent, shielded transactions sent for privacy coins, and transparent funds converted to shielded — `send-coins`, `zsend-coins`, `shield-coins`
- Balances checked, and any supported RPC command executed directly — `get-balance`, `execute-command`
- Daemon information and health — `check-status`
- Resources rather than tools for reference material: per-coin documentation, a daemon's own help text, and recent transaction history — `crypto://{coinType}/help`, `daemon://{name}/help`, `daemon://{name}/transactions`
- Prompt templates for constructing a transaction, analysing balances and fund distribution, and running a daemon health check — `send-transaction-template`, `balance-analysis`, `daemon-diagnostic`
- Several daemons configured side by side, each with its own coin name, nickname, RPC endpoint and credentials
A running daemon with RPC enabled — `server=1`, an `rpcuser` and `rpcpassword`, and `rpcallowip` set — and a JSON configuration file listing each daemon's `coinName`, `nickname`, `rpcEndpoint`, `rpcUser` and `rpcPassword`. Point the server at it with `CONFIG_PATH` in your client config. Node.js. The README launches it under the npm name `@raw391/coin-daemon-mcp` at 0.2.0-beta.1, which npm does not have; a Smithery entry is documented as well.