Cryptocurrency Major Mover Surveillance System

A Model Context Protocol (MCP) infrastructure component dedicated to monitoring significant cryptocurrency transfers utilizing the Whale Alert API

Table of Contents

• System Summary
• Capabilities
• System Requirements
• Setup Procedures
• Operational Guide
• Local Iterative Testing
• Integration with Claude Desktop Client
• Direct Service Invocation
• Interaction Examples
• Authentication Credential Configuration
• Legal Notice
• Acknowledgements

System Summary

The crypto-big-movers-monitor service operates as a Python-implemented instance conforming to the Model Context Protocol (MCP) specification. It establishes connectivity with the Whale Alert API to facilitate the continuous observation and analytical processing of substantial cryptocurrency movements, often termed "whale" activities. This component furnishes MCP-compliant front-ends, such as Claude Desktop, with necessary operational interfaces, contextual data resources, and standardized instructional templates.

This service targets financial technologists, blockchain auditors, and researchers aiming to embed high-volume asset movement surveillance directly within their Large Language Model (LLM) operational frameworks.

Capabilities

• Exposed Functions:
• fetch_recent_transfers: Retrieves a curated list of recent large-scale transfers, allowing optional refinement based on ledger system, minimum transfer valuation, and result count.
• retrieve_transfer_specification: Fetches exhaustive metadata pertaining to an individual transfer, referenced by its unique identifier.
• Contextual Data Sources:
• crypto://movements/{ledger_system}: Publishes recent transfer records associated with a designated blockchain as accessible contextual payloads.
• Predefined Instructional Templates:
• assess_capital_flow_patterns: A reusable template designed for the systematic analysis of capital movement characteristics, optionally parameterizable by blockchain identifier.
• Asynchronous Network Handling: Employs the httpx library to ensure non-blocking, efficient request execution against the Whale Alert service endpoint.
• Secure Credential Management: Supports the ingestion of sensitive API keys via a local .env configuration file.

System Requirements

• Runtime Environment: Python interpreter, version 3.10 or subsequent.
• API Credential: A valid access key obtained by registering on whale-alert.io.
• Client Platform: An MCP-compatible consumer application, such as Claude Desktop or the dedicated MCP Inspector utility.

Setup Procedures

Installation via Smithery

For automated deployment directly into Claude Desktop via Smithery:

bash npx -y @smithery/cli install @kukapay/whale-tracker-mcp --client claude

1. Repository Retrieval: bash git clone https://github.com/kukapay/whale-tracker-mcp.git cd whale-tracker-mcp

2. Dependency resolution: We advocate for the use of uv for dependency handling: bash uv add "mcp[cli]" httpx python-dotenv

Alternatively, utilizing standard pip: bash pip install mcp httpx python-dotenv

1. API Key Provisioning: Establish a .env file within the primary directory and populate it with your Whale Alert access token:

WHALE_ALERT_API_KEY=your_api_key_here

Operational Guide

Local Iterative Testing

Execute the service in a local development context, typically interfacing with the MCP Inspector:

bash mcp dev whale_tracker.py --with-editable .

This action launches a local web interface where the defined functions, resources, and templates can be explored.

Integration with Claude Desktop Client

Install the service directly into the Claude Desktop environment for smooth operational integration:

bash mcp install whale_tracker.py --name "WhaleTracker" -f .env

• --name "WhaleTracker": Assigns a bespoke label to the service within the Claude Desktop interface.
• -f .env: Instructs the installer to source authentication parameters from the specified environment file.

After installation, a restart of Claude Desktop is required. Verify successful loading by observing the tool icon (hammer) adjacent to the input area, then proceed with commands such as:

• "Display recent major transactions observed on the Bitcoin network."
• "Acquire comprehensive data for transaction reference 123456789."
• "Conduct an analysis of capital flow activities impacting Ethereum."

Direct Service Invocation

Run the service as a standalone Python application for custom deployments:

bash python whale_tracker.py

Or employ the dedicated MCP Command Line Interface:

bash mcp run whale_tracker.py

Interaction Examples

Illustrative scenarios detailing potential user input within the Claude Desktop environment:

Fetch Recent Transfers:

text Provide the most recent major capital transfers documented on the Ethereum ledger, restricted to movements exceeding $1,000,000 in value?

The underlying mechanism invokes fetch_recent_transfers using parameters ledger_system="ethereum" and min_value=1000000.

Get Transaction Details:

text Furnish all contextual details associated with identifier 123456789.

The service utilizes retrieve_transfer_specification to query and present the relevant transaction payload.

Analyze Capital Flow Patterns:

text Initiate an assessment of recent major transfers observed on the Bitcoin network.

The invocation of the assess_capital_flow_patterns template triggers a patterned analysis utilizing the data available at the crypto://movements/bitcoin resource.

Authentication Credential Configuration

The monitoring service mandates the presence of a valid Whale Alert access credential, which is automatically loaded from the environment variable named WHALE_ALERT_API_KEY.

To configure this requirement:

• Create a .env configuration file: text WHALE_ALERT_API_KEY=your_api_key_here

• Confirm that the python-dotenv package has been successfully installed (it is included in the listed dependencies).

• The service will automatically resolve this key upon initialization.

Alternatively, the credential can be supplied directly during the service installation phase:

bash mcp install whale_tracker.py -v WHALE_ALERT_API_KEY=your_api_key_here

Legal Notice

This software project is provided under the terms of the MIT License. Detailed terms are available in the accompanying LICENSE documentation file.

Acknowledgements

• Whale Alert: Gratitude for providing the foundational data interface for tracking cryptocurrency major movements.
• Model Context Protocol contributors: Appreciation for the standardized MCP specification and the Python SDK implementation.
• httpx maintainers: Thanks for the creation of a robust asynchronous HTTP client library.

Enjoy tracking the major capital flows! 🚀

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea