MODEL CONTEXT PROTOCOL

China Stock MCP Server

Connect QuantCoda market data to Claude, Cursor or another MCP client as hosted remote tools. Agents query China A-share data with explicit inputs instead of inferring answers from marketing pages.

Get a free API key Read the agent setup guide

Connect the remote China Stock MCP Server

The server is available at https://quantcoda.com/mcp. Send the same API key used by REST and Python as Authorization: Bearer ...; X-API-Key remains supported for compatible clients.

# Claude Code
claude mcp add --transport http quantcoda https://quantcoda.com/mcp \
  --header "Authorization: Bearer qc_live_your_key"

China Stock API for AI Agents

The same authenticated contract is available through the China A-Share Market Data API, the Python SDK and MCP. An agent can discover tools first, then request bounded market, ETF, financial or money-flow data without translating between separate field models.

45 MCP TOOLS

Data capabilities aligned with the API

Market, ETF, index, financial, valuation, money-flow, chip, realtime quote and news tools share one public contract.

STRUCTURED OUTPUT

Typed data and explicit metadata

Every tool returns structuredContent.data plus interface ID, row counts and truncation state in meta.

MACHINE DISCOVERY

Latest and legacy protocol support

The server negotiates MCP 2026-07-28 and earlier protocol revisions from the same endpoint.

READ-ONLY TOOLS

Explicit safety semantics

Every market-data tool is marked read-only, non-destructive and idempotent for compatible agents.

A hosted China market data API through remote MCP

QuantCoda runs the remote MCP endpoint, so compatible clients connect over HTTPS instead of starting a local market-data server. Review China stock API authentication and rate limits before adding the Bearer header, then use tool discovery to inspect names, parameters and minimum plan requirements.

Keep research workflows bounded

Prefer code-driven access?

Use the Python SDK for China Stock Data or the REST API documentation. All three interfaces retain the same symbol and field semantics.