MCP Server REST API & WebSocket Real-time Push Interface Financial Data API Documentation SDK & Developer Tools Official iTick MCP Server providing REST API queries and WebSocket real-time data subscriptions for basics, stocks, indices, futures, funds, forex, and cryptocurrencies.

Introduction to MCP Server

The official iTick MCP Server is a standardized protocol server launched by the iTick financial data platform, built on the Model Context Protocol (MCP). It provides a unified entry point for AI assistants (such as Claude Desktop, Cursor, etc.) to access financial data. This server encapsulates iTick's high-quality data capabilities in global forex, stocks, indices, futures, funds, and cryptocurrencies. It supports REST API batch queries and WebSocket real-time push notifications. Developers only need to configure an API Key to instantly call professional financial data within AI dialogue environments, significantly lowering the barrier to data integration.

Features

Developer-Friendly: Standardized and easy-to-use interfaces, concise documentation, and rich examples for quick integration.
Comprehensive Product Coverage: Real-time and historical data for multi-market stocks, forex, indices, cryptocurrencies, and more.
Versatile Scenarios: Suitable for quantitative teams, fintech applications, and professional analysis.
Robust Infrastructure & Service: Professional data sources, multi-region acceleration, and link hot backups, focusing on real-time performance and stability.
Customization: Institutional and professional users can negotiate customized data solutions.

iTick API Types and Project Scope

Type	Description	This MCP
REST	Retrieve quotes, K-lines, etc., via market data endpoints; requests must include authentication information such as tokens as per documentation.	Implemented (Only REST capabilities covered by HTTP GET)
Websocket	Publish/subscribe model pushing orders, trades, market data, etc., to reduce polling.	Not Implemented
FIX	High-throughput, institutional-grade connections; currently primarily for institutional clients.	Not Implemented (Non-REST)

For FIX access (institutional only), please contact official support: Telegram @iticksupport, WhatsApp +852 59046663.

Technical Support (Summary)

Email: [email protected] (Please include environment, identity, and problem description in the subject line)
Business Hours: Monday to Friday, 9:00–18:00 (Hong Kong Time); emergency production issues are subject to official announcements.
Non-Business Hours: Log in to itick.net to contact online customer service via instant messaging.

MCP Server

https://api.itick.net/mcp

Quick Configuration

Supported platforms:

✨ Cursor
✨ Claude Desktop
✨ OpenCode

Manual Configuration

Name	Description
`TOKEN`	Required in actual calls: request header `token`, see REST documentation

Cursor / Claude Desktop

{
  "mcpServers": {
    "itick": {
            "transport": "streamable_http",
            "url": "https://api.itick.net/mcp",
            "headers": {
                "token": "your_token"
            }
        }
  }
}

OpenCode

OpenCode uses the mcp key in opencode.json / opencode.jsonc. For local services, set type to "local", pass the startup command as a string array in command, and place environment variables in the environment field (this differs from Cursor's mcpServers / env structure). A minimal example is shown below:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "itick": {
      "type": "remote",
      "url":"https://api.itick.net/mcp",
      "headers": {
        "token": "your_token"
      },
      "enabled": true
    }
  }
}

langchain_mcp_adapters

from langchain_mcp_adapters.client import MultiServerMCPClient

itick_config = {
    "url": "https://api.itick.net/mcp",
    "transport": "streamable_http",
    "headers": {
        "token": "your_token",
    }
}

itick_mcp_client = MultiServerMCPClient({
    "itick": itick_config
})

async def get_itick_mcp_tools():
    itick_tool = await itick_mcp_client.get_tools()
    return itick_tool

MCP Tool Overview

Corresponds to paths in the REST documentation:

Basic

symbolList → GET /symbol/list
symbolHolidays → GET /symbol/v2/holidays

Stocks (Additional)

stockInfo → GET /stock/info
stockIpo → GET /stock/ipo
stockSplit → GET /stock/split

Product Lines (stock / crypto / forex / indices / future / fund)

Tool Name	REST
`{prefix}Tick`	`GET /{prefix}/tick`
`{prefix}Quote`	`GET /{prefix}/quote`
`{prefix}Depth`	`GET /{prefix}/depth`
`{prefix}Kline`	`GET /{prefix}/kline`
`{prefix}Ticks`	`GET /{prefix}/ticks`
`{prefix}Quotes`	`GET /{prefix}/quotes`
`{prefix}Depths`	`GET /{prefix}/depths`
`{prefix}Klines`	`GET /{prefix}/klines`

In batch interfaces, codes is a comma-separated list. K-line parameters in tools are k_type, encoded as kType in requests; optional et (timestamp in milliseconds), limit.

The tool name for single stock K-line remains stockKline as in the early Java example.