MCP Server

Access the official remote MCP server for Ashdata.

Overview

Your AI models and agents can use our official remote MCP server to access real-time financial data in a simple and secure way. Authentication is by API key (Bearer) and, when enabled on the server, by the Ashpay on-chain offer protocol for tools/call (see below).

  • Programmatic server: /api/mcp (POST JSON-RPC)
  • Streamable HTTP server: /mcp (GET SSE, POST JSON-RPC)
  • SSE server: /sse (GET event stream)
  • Discovery: /.well-known/ashpay.json (Ashpay / x402 availability)

示例:https://v3rse.cn + 上述路径

Installation

Connect via native Claude integration or use the mcp-remote module in Cursor, Windsurf, and other clients.

APIClaudeCursorVS CodeWindsurfZedCLI

MCP Tools

Available tools (A-share data): search_tickers (search by keyword),get_company_facts (company code, name, industry, sector),get_daily_bars (OHLCV daily bars),get_bars (1d/15m/30m/1h/4h),get_ticker, list_tickers. Authenticate with your API key from the Dashboard.

数据来源:以上工具与网站 API、Dashboard 共用同一套数据库。标的与 K 线由 Baostock 导入脚本写入(npm run ingest -- --fetchpython3 scripts/ingest_bars.pynpm run ingest:bars),跑过导入后 MCP 即可返回相同数据。

Fund Tracking Tools

Large fund holdings and block trade signal tools: get_fund_holdings (query large fund holdings — params: code?, fund_name?, report_date?, limit?), get_fund_holding_changes (query position changes — params: code?, fund_name?, report_date?, change_type?, limit?), search_fund_holdings (keyword search fund holdings — params: q, limit?), get_fund_block_trades (block trade signals — params: code?, start_date?, end_date?, limit?).

Authentication

Pass your API key in the request header or as configured in your MCP client. Create and manage keys in the Dashboard. Bearer is evaluated first; a valid key uses the standard usage/credits path.

Ashpay (on-chain) payment

The server implements the Ashpay offer protocol (xashpay-offer-v1) for optional x402-style payment on tools/call, alongside existing Bearer API keys. Point a local Ashpay-capable client (e.g. cc + Ashpay) at this site's /api/mcp or /mcp.

  • Unpaid tools/call may receive HTTP 402 with a JSON offer; pay on-chain, then retry with the Ashpay payment headers.
  • initialize / tools/list can be used without a Bearer for discovery when Ashpay is on.
  • /.well-known/ashpay.json describes whether Ashpay is enabled and related endpoints.
  • Valid Authorization: Bearer is unchanged and checked first.

Example Usage

{
  "mcp": "https://v3rse.cn/api/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}