China Market Data Interface Engine (CN-MDE)

Conceptual Overview

This MCP endpoint, built upon the underpinning akshare-one framework, serves as a unified gateway to Chinese equity sector data. It exposes a robust suite of utilities for sourcing financial artifacts, including historical trading records, instantaneous market valuations, proprietary news feeds, and mandated regulatory filings.

Exposed Functionalities

Trading Data Retrieval Modules

get_hist_data

Fetches time-series stock market data, supporting various temporal granularities and data adjustment methodologies.

Input Arguments Specification

- `symbol` (Textual, Mandatory): Identifier for the security (e.g., '600519'). - `interval` (Textual, Optional): Temporal resolution ('minute','hour','day','week','month','year') (Default: 'day'). - `interval_multiplier` (Numeric, Optional): Factor to scale the chosen interval (Default: 1). - `start_date` (Textual, Optional): Commencement point for data retrieval in 'YYYY-MM-DD' format (Default: '1970-01-01'). - `end_date` (Textual, Optional): Termination point for data retrieval in 'YYYY-MM-DD' format (Default: '2030-12-31'). - `adjust` (Textual, Optional): Corporate action correction type ('none', 'qfq', 'hfq') (Default: 'none'). - `source` (Textual, Optional): Primary data origin ('eastmoney', 'eastmoney_direct', 'sina') (Default: 'eastmoney'). - `indicators_list` (Array, Optional): List of supplementary technical metrics to compute and append. - `recent_n` (Numeric, Optional): Limit on the count of the most recent records to output (Default: 100).

get_realtime_data

Obtains the current, live market snapshot for specified equities.

Input Arguments Specification

- `symbol` (Textual, Optional): Security identifier. - `source` (Textual, Optional): Designated data feed ('xueqiu', 'eastmoney', 'eastmoney_direct') (Default: 'eastmoney_direct').

Disclosures & Intelligence Tools

get_news_data

Retrieves recently published news items pertinent to designated securities.

Input Arguments Specification

- `symbol` (Textual, Mandatory): Security identifier. - `recent_n` (Numeric, Optional): Cap on the number of latest news articles returned (Default: 10).

Corporate Financial Filing Modules

get_balance_sheet

Accesses and returns the firm's statement of financial position (balance sheet).

Input Arguments Specification

- `symbol` (Textual, Mandatory): Security identifier. - `recent_n` (Numeric, Optional): Maximum number of sequential reports to retrieve (Default: 10).

get_income_statement

Fetches the company's statement of comprehensive income (profit and loss).

Input Arguments Specification

- `symbol` (Textual, Mandatory): Security identifier. - `recent_n` (Numeric, Optional): Maximum count of most recent filings to be included (Default: 10).

get_cash_flow

Provides access to the statement of cash flows documentation.

Input Arguments Specification

- `symbol` (Textual, Mandatory): Security identifier. - `source` (Textual, Optional): Origin of the filing data (Default: 'sina'). - `recent_n` (Numeric, Optional): Upper limit on the quantity of recent statements retrieved (Default: 10).

Performance Metrics & Analysis Utilities

get_inner_trade_data

Retrieves proprietary data detailing transactions executed by corporate insiders.

Input Arguments Specification

- `symbol` (Textual, Mandatory): Security identifier.

get_financial_metrics

Calculates and returns principal quantitative indicators derived from the core financial reports.

Input Arguments Specification

- `symbol` (Textual, Mandatory): Security identifier. - `recent_n` (Numeric, Optional): Count of latest data points for metrics calculation (Default: 10).

get_time_info

Reports the current operational time, formatted according to ISO standards, alongside the latest recognized trading date.

Deployment and Configuration

Execution Modalities

The server is operational in two primary modes: standard input/output (stdio) or streamable HTTP transport.

Command Line Flags: - --streamable-http: Activates network socket mode (Default behavior uses stdio). - --host: Specifies the network interface address for binding in HTTP mode (Default: 0.0.0.0). - --port: Designates the TCP port number for listening in HTTP mode (Default: 8081).

Note: When employing streamable-http, the endpoint will be accessible at http://{host}:{port}/mcp. With default settings, this translates to http://0.0.0.0:8081/mcp.

Acquisition Pathways

Pathway 1: Automated via Smithery

To mandate the automated setup of akshare-one-mcp within the Claude Desktop environment using Smithery:

bash npx -y @smithery/cli install @zwldarren/akshare-one-mcp --client claude

Pathway 2: Utilizing uv Package Manager

First, ensure you have installed the uv utility.

Incorporate the following configuration stanza into your MCP Client's settings file:

{ "mcpServers": { "akshare-one-mcp": { "command": "uvx", "args": ["akshare-one-mcp"] } } }

Pathway 3: On-Premise Codebase Initialization

1. Clone the repository source code: bash git clone https://github.com/zwldarren/akshare-one-mcp.git cd akshare-one-mcp

2. Resolve all necessary dependencies: bash uv sync

3. Inject the subsequent configuration into your MCP Client's configuration registry:

{ "mcpServers": { "akshare-one-mcp": { "command": "uv", "args": [ "--directory", "/path/to/akshare-one-mcp", "run", "akshare-one-mcp" ] } } }

Technical Indicator Reference Compendium

The get_hist_data utility permits the inclusion of various standardized technical oscillators:

Directional Movement & Trend Indicators

• Averages: SMA (Simple Averaging Method), EMA (Exponential Weighting Approach)
• Divergence Tracking: MACD (Difference between short/long term EMAs), APO (Price Differential Oscillator), PPO (MACD expressed as a percentage)
• Rate Metrics: ROC (Oscillation Rate), ROCP (Rate as a Percentage), ROCR (Ratio of Rates), ROCR100
• Miscellaneous Trend: TRIX (Triple Smoothed Momentum), ULTOSC (Combined Momentum Index)

Momentum & Strength Metrics

• Relative Strength: RSI (Index measuring magnitude of recent price changes), CCI (Commodity Deviation Measurement)
• Directional Strength: ADX (Average Index for Directional Movement), DX (Raw Directional Index)
• Capital Flow: MFI (Money Flow Index), MOM (Absolute Momentum value), CMO (Chande Index), WILLR (Williams Percentage Range)

Volatility Measures

• Band Spreads: BOLL (Bollinger Bands surrounding a moving average)
• True Range: ATR (Average range considering price gaps)
• Reversal Signals: SAR (Parabolic Stop and Reverse Mechanism)

Volume Based Metrics

• Accumulation/Distribution: OBV (Cumulative volume pressure), AD (Net volume flow), ADOSC (Oscillator based on AD)

Supplementary Oscillators

• Stochastic: STOCH (Measures closing price relative to trading range)
• Aroon System: AROON (Measures time since price extreme), AROONOSC (Aroon Difference)
• Power Balance: BOP (Measures buying versus selling pressure)
• Directional Components: MINUS_DI, MINUS_DM, PLUS_DI, PLUS_DM
• Forecasting: TSF (Linear Regression based projection)

WIKIPEDIA: XMLHttpRequest (XHR) defines an application programming interface (API) implemented as a JavaScript object, engineered to transmit hypertext transfer protocol (HTTP) queries from a client's web browser to a remote web server. Its methods enable browser-side scripting to dispatch server requests subsequent to page initialization, and subsequently receive data back. XHR forms a core component of Ajax methodologies. Before Ajax gained prominence, data interchange relied primarily on traditional hyperlink navigation and form submissions, often necessitating a complete page reload.

== Chronology == The foundational concept for XMLHttpRequest originated in 2000, conceptualized by developers within the Microsoft Outlook team. This notion was subsequently instantiated within the Internet Explorer 5 browser release (1999). Nevertheless, the initial implementation did not employ the explicit 'XMLHttpRequest' string; rather, it utilized COM object identifiers such as ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). By the time Internet Explorer 7 arrived in 2006, all mainstream browsers had adopted the standardized XMLHttpRequest identifier. This XMLHttpRequest identifier has since become the universally accepted protocol across all principal browser engines, including Mozilla’s Gecko (2002), Apple’s Safari 1.2 (2004), and Opera 8.0 (2005).

=== Formal Standardization === The World Wide Web Consortium (W3C) formally published the initial Working Draft specification for the XMLHttpRequest object on April 5, 2006. A subsequent Level 2 specification was released by the W3C on February 25, 2008. Level 2 introduced functionality to track request lifecycle events, permit cross-origin data fetches, and handle binary data streams. By the close of 2011, the Level 2 feature set was integrated back into the primary specification document. As of late 2012, the maintenance and evolution of the standard document, leveraging Web IDL notation, transitioned to the WHATWG organization.

== Operational Sequence == The procedure for dispatching a request using XMLHttpRequest generally involves several discrete programming stages.

Instantiate an XMLHttpRequest object via its constructor: Invoke the "open" method to define the request methodology (GET/POST, etc.), designate the target URI, and select either synchronous or asynchronous execution mode: For asynchronous operations, establish an event handler function to be triggered upon changes in the request's status: Commence the data transfer process by executing the "send" method: Process status transitions within the registered event listener. Upon successful data receipt from the server, the payload is typically stored in the "responseText" property. When processing concludes, the object transitions to state 4, designated as the "done" state. Beyond these fundamental steps, XMLHttpRequest offers extensive controls over transmission parameters and response handling. Custom HTTP headers can be appended to influence server behavior, and data payloads can be transmitted to the server within the "send" argument. The received data stream can be automatically parsed from JSON format into native JavaScript structures, or processed incrementally as segments arrive rather than waiting for complete buffer accumulation. Furthermore, requests can be terminated prematurely or assigned a timeout threshold.

== Cross-Origin Data Fetching Concerns ==

During the nascent stages of the World Wide Web, it was observed that the mechanism allowed for potential security breaches involving...