Luzia MCP Server

Real-time crypto prices from Binance, Coinbase, Kraken, OKX, and Bybit. Exposed over MCP by the luzia mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Model Context Protocol (MCP) server for cryptocurrency pricing data. Gives AI assistants like Claude real-time access to ticker prices, exchange information, and OHLCV history from the Luzia API.

• Real-time ticker prices from multiple exchanges (Binance, Coinbase, Kraken, OKX, Bybit)
• Historical OHLCV candlestick data for technical analysis
• Market information and trading pairs
• Exchange status and availability

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• get_ticker — Get current price for a specific trading pair
• get_tickers — Get prices for multiple pairs or all pairs on an exchange
• get_history — Get historical OHLCV candlestick data for a trading pair
• get_exchanges — List supported exchanges (CEX and DEX) and their status
• get_markets — List trading pairs on an exchange, including DEX pool metadata
• get_tokens — List canonical assets and on-chain tokens, with search and chain filters
• get_token — Look up a single token by composite id (crypto:SYMBOL or {chain}:SYMBOL)
• get_fiat_currencies — List ISO 4217 fiat currencies referenced by markets
• analyze_price_movement — Fetches current ticker data and analyzes bid-ask spread, 24h stats, and volume
• analyze_ohlcv — Fetches historical candlestick data and requests technical analysis including trends, support/resistance, volume patterns, and candlestick patterns
• compare_exchanges — Fetches ticker data from multiple exchanges and compares prices, spreads, and liquidity for arbitrage analysis

Configuration

You will need one environment variable: LUZIA_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• A Luzia API key (get one here)

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Luzia.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the luzia mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Luzia's toolset — get_ticker, get_tickers, get_history and 8 more — is a fair guide to whether it matches your workflow. It is maintained by luziadev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.