Digital Asset Data Interface (DADI)

This implementation serves as a cryptographic asset price retrieval engine adhering to the Model Context Protocol (MCP). It furnishes diverse functionalities for obtaining virtual currency valuations, prevailing market movements, granular asset specifics, and historical OHLC (K-line) records.

Table of Contents

• Setup
• Operational Guide
• Tooling Index
• References
• Licensing

Setup

Installation via PyPI

Execute the following command in your terminal:

bash pip install crypto_mcp

Installation via Smithery [Recommended Path]

To integrate DADI with Claude Desktop automatically using Smithery, run:

bash npx -y @smithery/cli install @telegramtool/crypto_mcp --client claude

Alternative deployment methods are detailed here.

Manual Bootstrap

Clone the repository and install necessary dependencies:

bash git clone https://github.com/telegramtool/crypto_mcp.git cd crypto_mcp pip install -r requirements.txt

Operational Guide

Configuration within Cursor IDE

Integrate the subsequent configuration block into your ~/.cursor/mcp.json file:

PIP Installation Configuration:

{ "mcpServers": { "crypto_mcp": { "command": "uv", "args": [ "run", "-m", "crypto_mcp"] } } }

Smithery Installation Configuration:

{ "mcpServers": { "crypto_mcp": { "command": "cmd", "args": [ "/c", "npx", "-y", "@smithery/cli@latest", "run", "@telegramtool/crypto_mcp", "--config", "{}" ] } } }

Tooling Index

CoinGecko and Bitget Interface Modules

• get_coin_price - Retrieves the instantaneous valuation for a specified digital asset.
• get_trending_coins - Fetches a roster of currently popular cryptocurrencies.
• get_coin_detail - Obtains exhaustive descriptive data pertaining to a cryptocurrency.
• get_global_market_data - Accesses overarching metrics for the worldwide crypto economy.
• search_coins - Performs a lookup for matching digital assets.
• get_common_coins_prices - Queries current price points for a curated selection of prominent assets.
• get_k_line_data - Retrieves time-series charting data (OHLC bars) for an asset.

Coinglass Derivative Market Modules

• coinglass_get_coin_info - Fetches derivative contract specifications for an asset.
• coinglass_get_kline_data - Retrieves K-line data specifically for derivative instruments.
• coinglass_get_position_info - Queries information regarding open interest and contract positioning.
• coinglass_get_trade_volume - Retrieves metrics related to the volume of contract trading.
• coinglass_get_trade_amount - Fetches the aggregated monetary value of contract trades.
• coinglass_get_exchange_position - Determines the distribution of contract holdings across various exchanges.

References

• CoinGecko Data Service Portal
• Bitget API Documentation
• Coinglass Market Analytics Platform

Licensing

This software project is distributed under the permissive MIT License terms.

WIKIPEDIA: XMLHttpRequest (XHR) constitutes an Application Programming Interface implemented as a JavaScript object. Its methods facilitate the transmission of HTTP requests originating from a web browser targeting a web server. These functionalities permit browser-resident applications to dispatch server queries subsequent to initial page rendering and receive resultant data asynchronously. XMLHttpRequest is foundational to Ajax programming techniques. Prior to Ajax adoption, standard hyperlinks and form submissions served as the principal means of server interaction, frequently necessitating a complete page refresh upon completion.

== Genesis == The foundational concept underlying XMLHttpRequest emerged in the year 2000, conceived by software architects involved with Microsoft Outlook. This idea was subsequently incorporated into the Internet Explorer 5 browser release (1999). Notably, the initial implementation did not utilize the 'XMLHttpRequest' identifier. Instead, developers employed the constructor invocations ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). With the introduction of Internet Explorer 7 (2006), universal browser support for the 'XMLHttpRequest' identifier became standard. The XMLHttpRequest identifier has since established itself as the prevailing convention across all major browser engines, including Mozilla’s Gecko rendering engine (2002), Safari version 1.2 (2004), and Opera version 8.0 (2005).

=== Formal Specifications === The World Wide Web Consortium (W3C) formally published a Working Draft specification detailing the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C released the Working Draft specification for Level 2. Level 2 enhancements introduced methods for monitoring request progress, enabling cross-site data fetching, and managing byte-level data streams. By the close of 2011, the Level 2 specification elements were consolidated back into the original primary document. As of late 2012, development oversight transitioned to the WHATWG, which currently maintains a dynamic document based on Web IDL standards.

== Operational Procedure == Generally, issuing a network request via XMLHttpRequest involves a sequence of distinct programming actions.

1. Instantiate an XMLHttpRequest object by invoking its constructor method:
2. Invoke the "open" method to specify the request protocol (e.g., GET/POST), designate the target resource Uniform Resource Identifier (URI), and select between synchronous or asynchronous execution mode:
3. For asynchronous operations, establish an event handler to receive notifications whenever the request's status undergoes modification:
4. Commence the transmission by executing the "send" method:
5. Process state transitions within the assigned event handler. If the server furnishes response content, it is typically stored, by default, within the "responseText" attribute. Once the object completes processing the response cycle, its state transitions to 4, signifying the 'done' status. Beyond these fundamental steps, XMLHttpRequest provides extensive configurability for controlling request origination and response parsing. Custom HTTP headers can be appended to modify server behavior, and data payloads can be uploaded by supplying them as an argument to the "send" call. The returned data can be immediately parsed from JSON string format into native JavaScript objects, or it can be processed incrementally as it streams in, avoiding a mandatory wait for the complete payload. Furthermore, the request can be terminated preemptively or configured with a timeout limit to ensure failure if completion is not achieved promptly.

== Inter-Origin Communication ==

During the nascent stages of the World Wide Web's evolution, limitations were discovered that restricted the ability to successfully tran