🔗 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:
| Area | What you can do |
|---|---|
| Metadata discovery | List supported exchanges and enumerate symbols per exchange. |
| OHLCV timeseries | Inspect supported candle periods, fetch latest candles, retrieve historical candles, or pull exchange-wide OHLCV windows. |
| Native IEX datasets | Access 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:
- Call
stock_exchanges_listto find a venue such asIEXG,XWAR, orXHKG. - Call
stock_symbols_listwith the selectedexchange_id. - Call
stock_ohlcv_periods_listto discover valid candle granularities such as1MIN,1DAY, or1MTH. - Use
stock_ohlcv_latestorstock_ohlcv_historyfor symbol-level OHLCV data. - Use the
stock_native_iex_*tools when you need market microstructure data from IEX.
Live-tested notes
stock_ohlcv_latestreturns rows in descending time order.stock_ohlcv_historyreturns rows in ascending time order.stock_ohlcv_history_by_exchangerequires bothtime_startandtime_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.
