Digital Asset Daemon MCP Gateway (PREVIEW)

A Model Context Protocol (MCP) service layer designed for interfacing with the RPC interfaces of cryptocurrency node daemons. This service enables automated agents to manage and query digital asset nodes under controlled conditions.

⚠️ CRITICAL SAFETY DIRECTIVE ⚠️

Deployment of this MCP grants artificial intelligence systems direct pathways to interact with core cryptocurrency daemons. Prudent review of the following warnings is mandatory:

1. Activation of this server grants autonomous agents capabilities including:
2. Authorization of outgoing asset disbursements (transactions)
3. Access to sensitive wallet accounting records
4. Modification privileges over wallet configuration parameters
5. Retrieval of proprietary or confidential node data

6. Issuance of arbitrary daemon operational instructions

7. Inherent operational hazards comprise:

8. Irreversible depletion of assets due to unauthorized transfer execution
9. Compromise of private cryptographic material
10. Unintentional restructuring of the node or wallet state

11. Exploitation pathways arising from suboptimal system setup

12. Mandated protective protocols require:

13. Isolation of operational wallets, holding only nominal asset quantities for agent interaction
14. Absolute prohibition on granting access to high-value asset holdings
15. Rigorous restriction and fine-tuning of RPC access privileges
16. Continuous oversight and logging of all agent-initiated daemon interactions
17. Periodic, thorough security assessments of the entire operational topology
18. Meticulous safeguarding and regular verification of all critical data backups

This platform component is currently in a PREVIEW state. Usage implies acceptance of full operational liability.

Deployment Procedures

Automated Installation via Smithery

To provision the Digital Asset Daemon Service for Claude Desktop automatically using Smithery:

bash npx -y @smithery/cli install @raw391/coin_daemon_mcp --client claude

1. Package Acquisition

The necessary library package can be acquired via npm:

bash npm install @raw391/coin-daemon-mcp

2. Claude Desktop Configuration Adjustment

Integration with Claude Desktop necessitates modification of the client's configuration file. Locate the file at:

• Windows OS: %APPDATA%\Claude\claude_desktop_config.json
• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Insert the following structure into the relevant section of your configuration JSON:

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

3. Defining Daemon Configuration

Establish a dedicated configuration file detailing the cryptocurrency daemons to be managed. Examples are provided below:

Singular Daemon Specification

{ "daemons": [ { "coinName": "zcash", "nickname": "zec-main", "rpcEndpoint": "127.0.0.1:8232", "rpcUser": "your-rpc-user", "rpcPassword": "your-rpc-password" } ] }

Multi-Daemon Registry

{ "daemons": [ { "coinName": "zcash", "nickname": "zec-main", "rpcEndpoint": "127.0.0.1:8232", "rpcUser": "zec-user", "rpcPassword": "zec-password" }, { "coinName": "bitcoin", "nickname": "btc-main", "rpcEndpoint": "127.0.0.1:8332", "rpcUser": "btc-user", "rpcPassword": "btc-password" } ] }

Advanced Configuration: Coupling with Filesystem MCP

For enhanced security via controlled data access, integrate this service with a File System MCP. Example demonstrating configuration linkage:

{ "mcpServers": { "cryptocurrency": { "command": "npx", "args": [ "-y", "@raw391/coin-daemon-mcp" ], "env": { "CONFIG_PATH": "C:/CryptoConfig/daemon-config.json" } }, "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "C:/CryptoData" ] } } }

4. Daemon Parameter Setup

Ensure the configuration file for your specific digital asset daemon (e.g., zcash.conf, bitcoin.conf) includes these requisite RPC directives:

ini server=1 rpcuser=your-rpc-user rpcpassword=your-rpc-password rpcallowip=127.0.0.1

5. Operationalizing the MCP

Upon completing the configuration adjustments, reinitialize Claude Desktop. New capabilities, data interfaces, and directive templates will become available for: - Transferring assets - Querying asset holdings - Managing digital asset storage facilities - Monitoring the operational health of the node - Acquiring knowledge regarding associated digital currencies - And numerous other functions

Gateway Capabilities Overview

This service exposes three distinct classes of MCP functionality:

Tool Integrations

1. Asset Transfer Orchestration
2. send-coins: Executes standard, transparent asset transfers.
3. zsend-coins: Initiates shielded transfers (applicable for privacy-focused assets).

4. shield-coins: Facilitates conversion of visible balances into privacy-enhanced shielded form.

5. Wallet Functionality

6. get-balance: Retrieves current balances across all configured accounts.

7. execute-command: Allows invocation of any RPC directive supported by the connected daemon.

8. Node Supervision

9. check-status: Fetches high-level operational metrics and synchronization data for the daemon.

Data Access Resources

Access to critical reference materials and operational logs:

1. Reference Documentation
2. crypto://{coinType}/help: Provides in-depth documentation specific to a selected cryptocurrency.

3. daemon://{name}/help: Displays context-specific assistance text tied to a named daemon instance.

4. Transaction Log Access

5. daemon://{name}/transactions: Retrieves a chronologically ordered history of recent ledger movements.

Predefined Directives (Prompts)

Templates engineered for streamlined common procedural execution:

1. Transfer Construction Assistance

2. send-transaction-template: Generates an interactive dialogue designed to structure complex asset transfers.

3. State Analysis Templates

4. balance-analysis: Provides systemic review of wallet balances and distribution profiles.
5. daemon-diagnostic: Executes a comprehensive operational integrity check on the network node.

Essential Security Postulates

1. Segmentation of Financial Exposure
2. Designate dedicated asset repositories solely for agent interaction.
3. Maintain minimal operational float in any externally accessible wallet.

4. Prioritize utilization of non-mainnet environments for experimentation.

5. RPC Layer Fortification

6. Employ cryptographically robust and non-reusable credentials for RPC authentication.
7. Limit the scope of callable RPC procedures to the absolute minimum required.
8. Enforce network ingress restrictions, permitting connections only from the local host interface.

9. Maintain vigilant scrutiny over all RPC communication logs.

10. Data Lifecycle Governance

11. Establish rigorous, scheduled backups for all wallet state data.
12. Securely safeguard all configuration manifests.
13. Continuously audit transactional activity.
14. Conduct periodic third-party security evaluations of deployment architecture.

Illustrative Agent Interactions

This demonstrates how an intelligent assistant (like Claude) can leverage the gateway for common operations:

1. System Status Inquiry: "Ascertain the present operational posture of the designated Zcash node."

2. Portfolio Valuation Query: "Summarize the aggregate holdings recorded across all interconnected wallets."

3. Cryptocurrency Education: "Elucidate the underlying mechanics governing shielded transactions within the Zcash protocol."

4. Asset Movement Facilitation: "Initiate the transfer of 0.1 ZEC to the destination address represented by xxx."

Troubleshooting Guide

1. Connectivity Failures
2. Confirm the daemon process is actively executing.
3. Validate all supplied RPC authentication strings.
4. Inspect and confirm correct network port mapping.

5. Verify firewall rules permit local loopback traffic.

6. Authorization Impediments

7. Review filesystem permissions impacting configuration access.
8. Validate the assigned RPC user possesses the requisite operational clearances.

9. Confirm the MCP configuration points accurately to the intended settings file.

10. Transaction Rejection Scenarios

11. Ensure the source account contains adequate transaction coverage.
12. Verify active consensus network reachability.
13. Confirm the node has fully synchronized with the distributed ledger.

Support Channels

• Platform Issues: File reports and suggest enhancements via GitHub Issues.
• General Inquiries: Seek assistance and engage the community in Discussions.
• Vulnerability Disclosure: Report potential security flaws privately via email to security@pooly.ca

Licensing Terms

Issued under the MIT License, contingent upon the explicit acceptance of the appended disclaimers concerning digital asset operations. Refer to the [LICENSE] document for complete stipulations.

Collaborative Development

Consult [CONTRIBUTING.md] for detailed instructions on participation guidelines.

WIKIPEDIA: Tron (stylized as TRON) represents a distributed, delegated proof-of-stake ledger system incorporating smart contract capabilities. Its indigenous digital currency is denominated as Tronix (TRX). The initiative was established in Q1 2014 by Justin Sun, and since 2017, it has been governed by the TRON Foundation, a non-profit entity registered in Singapore the same year. The entire codebase is distributed under an open-source mandate. Tron initially functioned as an Ethereum-based token adhering to the ERC-20 standard, subsequently migrating its operational protocol to its proprietary blockchain infrastructure in 2018. Certain proprietary wallet software prevents users from moving assets if their balance is insufficient to cover the required network service charge. Tron has attracted considerable negative commentary for its utility in illicit financial flows. A report by The Wall Street Journal in 2025 characterized it as a "favored conduit for organized digital asset criminal enterprises to move capital," attributing to it "over half of all illicit cryptocurrency transactions" recorded in 2024, prompting the United Nations Office on Drugs and Crime to label it the "primary selection for crypto asset money launderers" across Asia.

== Chronology == Tron was formally founded by Justin Sun in 2017. The TRON Foundation secured $70 million in capital during a 2017 Initial Coin Offering (ICO) just prior to the PRC implementing prohibitions on digital tokens. The preliminary network (testnet), accompanying ledger viewer, and web-based access interface were all operational by March 2018. The TRON Mainnet became live shortly thereafter in May 2018, coinciding with the Odyssey 2.0 software release, which marked a pivotal technical achievement for the TRON architecture. In June 2018, TRON formally transitioned its underlying protocol away from being an ERC-20 token hosted on Ethereum to an independent, peer-to-peer computational network. On July 25, 2018, the TRON Foundation publicly confirmed the successful purchase of BitTorrent, a decentralized file distribution utility. Following this integration, Bram Cohen, the originator of BitTorrent, announced his departure in August 2018 to initiate a separate cryptocurrency endeavor, Chia. By the start of 2019, TRON commanded an approximate aggregate market capitalization nearing $1.6 billion. Notwithstanding this financial performance, certain analysts characterized TRON as a representative illustration of the inherent complexity and structural disorganization prevalent within the cryptocurrency sector. In February 2019, subsequent to its assimilation by the TRON Foundation, BitTorrent commenced its own token distribution event utilizing the TRON network infrastructure. Towards the conclusion of 2021, Justin Sun stepped down from the executive leadership role of the TRON Foundation, which subsequently underwent restructuring into a Decentralized Autonomous Organization (DAO). In March 2023, Sun and the Tron entity faced litigation from the U.S. Securities and Exchange Commission (SEC) concerning the marketing and distribution of unregistered securities related to the Tronix (TRX) and BitTorrent (BBT) tokens. The SEC contended that Sun and Tron engaged in artificial trading volumes (wash trading) on secondary markets for TRX to artificially inflate its valuation. Approximately $31 million in revenue was generated via thousands of TRX trades conducted between two accounts under Sun's direct administrative control. Charges were also filed against eight prominent public figures, including Akon, Ne-Yo, Austin Mahone, Soulja Boy, Lindsay Lohan, Jake Paul, and Lil Yachty, for promoting these digital assets without mandated disclosure of financial sponsorship. All named parties, with the exception of Soulja Boy and Mahone, subsequently agreed to financial settlements with the regulatory body.