🔗 MCP API

Introduction

Use the FinFeedAPI Stock Historical MCP server to discover exchanges, symbols, OHLCV series, and native IEX datasets through self-describing tools.

Stock API MCP

The FinFeedAPI Stock Historical API is available through a hosted Model Context Protocol (MCP) server at https://api-historical.stock.finfeedapi.com/mcp. It exposes the Stock API as self-describing tools, which makes it easy to use from MCP clients such as Cursor, Claude Desktop, or custom agent runtimes.

Use your regular FinFeedAPI API key in the X-APIKey header.

What is available through MCP?

The Stock API MCP server currently exposes 11 tools grouped into three areas:

AreaWhat you can do
Metadata discoveryList supported exchanges and enumerate symbols per exchange.
OHLCV timeseriesInspect supported candle periods, fetch latest candles, retrieve historical candles, or pull exchange-wide OHLCV windows.
Native IEX datasetsAccess system events, admin messages, Level 1 quotes, Level 2 price levels, Level 3 order book updates, and trades.

Typical discovery flow

Most integrations follow this order:

  1. Call stock_exchanges_list to find a venue such as IEXG, XWAR, or XHKG.
  2. Call stock_symbols_list with the selected exchange_id.
  3. Call stock_ohlcv_periods_list to discover valid candle granularities such as 1MIN, 1DAY, or 1MTH.
  4. Use stock_ohlcv_latest or stock_ohlcv_history for symbol-level OHLCV data.
  5. Use the stock_native_iex_* tools when you need market microstructure data from IEX.

Live-tested notes

  • stock_ohlcv_latest returns rows in descending time order.
  • stock_ohlcv_history returns rows in ascending time order.
  • stock_ohlcv_history_by_exchange requires both time_start and time_end, and the requested window cannot exceed 24 hours.
  • Native IEX tools are date-sensitive. If there is no data for the chosen symbol and day, the MCP server returns an explicit error instead of an empty partial payload.

Start here

Service StatusGitHub SDK