# eliasfire617/crypto-market-data-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/eliasfire617/crypto-market-data-mcp  
**GitHub Stars:** 2  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/eliasfire617-crypto-market-data-mcp

## Description
Live crypto market data — price, funding rates, open interest, long/short ratio, order book, candles — across Bybit, Binance, OKX, Hyperliquid, Gate, KuCoin via CCXT, with funding-rate arbitrage comparison.

## Tools
Capabilities this server exposes over MCP:

- **list_exchanges** — Which exchanges are supported
- **get_capabilities** — Matrix of which exchange supports which data (no network)
- **search_symbols** — Find the exact symbol format for a coin
- **get_price** — Last price + 24h stats
- **get_order_book** — Top-of-book bids/asks
- **get_ohlcv** — Recent OHLCV candles
- **get_recent_trades** — Latest public trades
- **get_funding_rate** — Current perpetual funding rate
- **get_funding_rate_history** — Historical funding rates
- **compare_funding** — Funding rate across many exchanges + **arb spread
- **get_open_interest** — Current open interest
- **get_long_short_ratio** — Global long/short account ratio (Binance)
- **get_liquidations** — Recent public liquidations (limited support)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "crypto-market-data-mcp": {
    "command": "npx",
    "args": ["-y","mcpize"]
  }
}
```

## Documentation

## What eliasfire617/crypto-market-data-mcp MCP server does

The eliasfire617/crypto-market-data-mcp MCP server gives MCP-compatible agents read-only access to public cryptocurrency market data. It is built around CCXT and currently lists Bybit, Binance, OKX, Hyperliquid, Gate, and KuCoin as supported exchanges. The implementation can be extended by adding more CCXT exchange IDs to its supported-exchange configuration.

Its tools cover both spot and derivatives use cases. Agents can discover supported venues, inspect data capabilities without making a network request, and normalize common symbol forms such as `btc`, `BTCUSDT`, and `BTC-USDT`. Market-data tools return prices, 24-hour statistics, order-book levels, OHLCV candles, and recent public trades. Derivatives tools provide current and historical funding rates, open interest, Binance global long/short account ratios, and recent liquidations where supported.

## How it works

Requests are sent to exchange public endpoints, so API keys are not needed for local stdio operation. The server checks whether an exchange supports the requested method before making the call and returns structured errors when a capability is unavailable. Responses use a short-lived cache, and transient network failures are retried with exponential backoff for up to three attempts. Per-request and overall timeouts help prevent a slow exchange from blocking a tool call.

The `compare_funding` tool queries multiple exchanges and calculates an arbitrage spread. It converts funding values to annualized percentages before comparing them, accounting for different funding intervals such as Hyperliquid’s hourly schedule and the eight-hour schedule used elsewhere. This is useful for comparing venue-level funding, but it does not execute trades or manage positions.

## Setup and configuration

For local development, create a Python virtual environment, install the dependencies from `requirements.txt`, and start the server with `python server.py`. The local process uses stdio and is intended for clients such as Claude Desktop, Cursor, and Cline. A sample Claude Desktop configuration is included in the repository and requires local paths to be adjusted. Windsurf is also identified as a compatible MCP client in the project documentation.

The eliasfire617/crypto-market-data-mcp MCP server can alternatively start a streamable HTTP transport with `python server.py --http`. HTTP mode binds to port 8000 by default, with `PORT` available to override it. In this mode, clients send bearer API keys. Keys can be supplied inline through `CRYPTO_MCP_API_KEYS` or through a file selected with `CRYPTO_MCP_API_KEYS_FILE`. If no keys are configured, the server creates a temporary demo key for testing. Deployments behind an authenticated gateway can set `CRYPTO_MCP_DISABLE_AUTH=1` to skip the server’s own authentication and rate limiting.

## Tools and capabilities

Discovery tools include:

- `list_exchanges` for the supported exchange list.
- `get_capabilities` for an exchange-by-data capability matrix.
- `search_symbols` for locating exchange-specific symbol formats.

Market tools include `get_price`, `get_order_book`, `get_ohlcv`, and `get_recent_trades`. Derivatives tools include `get_funding_rate`, `get_funding_rate_history`, `compare_funding`, `get_open_interest`, `get_long_short_ratio`, and `get_liquidations`.

The server validates inputs and clamps limits on every tool. Logs are written to stderr so they do not interfere with stdio protocol traffic. Exchange cleanup is performed after requests, including when an exchange returns an error.

## Limitations and notes

This server is read-only and uses public market data; it does not place orders, access private account information, or execute arbitrage. Exchange support varies by method, and liquidation data has limited support. The long/short account ratio tool is specifically based on Binance data. HTTP mode has separate request-per-minute and monthly quotas for free, pro, and ultra tiers, while local stdio does not require authentication.

The roadmap mentions additional exchange support, more aggressive caching, and optional WebSocket streaming, but these are not described as current capabilities.

_Full upstream README: https://allmcps.com/mcp/eliasfire617-crypto-market-data-mcp/readme_