Cryptocurrency Daemon

Provides an MCP server to manage cryptocurrency daemons via RPC, enabling AI-assisted transactions, balance checks, and daemon control.

javascript

1

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "raw391-coin_daemon_mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@raw391/coin-daemon-mcp"
      ],
      "env": {
        "CONFIG_PATH": "path/to/your/config.json"
      }
    }
  }
}

You can use the Cryptocurrency Daemon MCP Server to safely interface AI assistants with your cryptocurrency daemons. It exposes structured tools to manage transactions, wallets, and daemon status, while keeping configuration and access controlled for safety and auditability.

How to use

You interact with the MCP server through an MCP client or integration that can run the provided stdio-based server wrapper. The server exposes three broad capability areas: Tools for performing operations like sending coins or querying balances, Resources for documentation and transaction history, and Prompts that guide common workflows. Start by ensuring your daemon RPC endpoints are reachable, then launch the MCP wrapper and configure your client to point at the local MCP instance. With the server running, you can request status, manage balances, execute RPC commands, and initiate transactions through clearly defined tool prompts.

How to install

# Prerequisites
- Node.js (recommended latest LTS) installed on your system
- npm (comes with Node.js) or npx available

# Step 1: Install the MCP server package
npm install @raw391/coin-daemon-mcp

# Step 2: (Optional) Install via Smithery for automated setup
npx -y @smithery/cli install @raw391/coin_daemon_mcp --client claude

# Step 3: Configure your client (Claude Desktop in this example)
# Create or edit your Claude Desktop config to include the MCP server
# The example uses a local MCP wrapper with a path to a config file

"} ]},{

## Configuration and security

Security is essential when enabling AI access to cryptocurrency daemons. Use a dedicated wallet with limited funds for AI interactions, restrict RPC permissions, and monitor all AI actions. Keep backups of important data and perform regular security audits. Ensure RPC credentials are strong and access is limited to localhost where possible.

Key configuration details shown below include how to run the MCP wrapper and point it to a local configuration file that lists your daemons. The path to the configuration file is provided via an environment variable named CONFIG\_PATH.

## Troubleshooting

Connection issues: Ensure the MCP wrapper and daemon RPC endpoints are running and that RPC credentials match. Verify ports and localhost access. Permission issues: Confirm file permissions and correct RPC user rights. Transaction issues: Check funds, network status, and that the daemon is synced.

## Example usage

Ask the MCP for quick tasks like checking your balance, getting daemon status, or guiding you through constructing a transaction. Examples include asking for the current daemon status, querying balances, or initiating a small test transfer.

## Available tools

### send-coins

Send transparent transactions to a recipient from your wallet.

### zsend-coins

Send shielded transactions for privacy-focused coins.

### shield-coins

Convert transparent funds into shielded funds for enhanced privacy.

### get-balance

Check your wallet or daemon balances across addresses.

### execute-command

Execute any supported RPC command against a configured daemon.

### check-status

Query daemon health and status information.