Skip to main content
The Everstrike MCP server connects any MCP-capable AI client to live exchange data. It exposes prices, order books, recent trades, candlestick history, funding rates, and exchange status as tools that an AI model can call during a conversation — so instead of guessing at market conditions, your assistant fetches the real answer. The server is read-only and requires no account or API key.
This server exposes public market data only. No tool can place, modify, or cancel orders, and no tool reads your account. Connecting this server cannot move your funds.

Quick Start

1

No setup required

The Everstrike MCP server is public and requires no API key, account, or signup. The server URL is:
2

Add the server to your client configuration

Add the following to your Claude Desktop or Cursor MCP configuration file:
3

Restart your client

Restart Claude Desktop or Cursor. You should see ten everstrike_* tools become available in your client.

cURL Example

The server speaks JSON-RPC over HTTP. Use the following commands to explore available tools and call one: List all tools:
Call a tool (fetch live BTC/USD price):
The Accept header must list both application/json and text/event-stream. Omitting either one causes the request to be rejected with a 406 error.

Market Naming

Everstrike uses a quote-first key convention for perpetual markets. The BTC/USD perpetual is USD_BTC_PERP, not BTC_USD_PERP. Spot markets run base-first, so the ordering depends on the instrument type.
The server resolves several friendly spellings automatically against the live market list: A bare asset name like XRP is ambiguous — the server cannot tell whether you mean the USD perpetual, a spot market, or an option. Send USD_XRP_PERP or XRP/USD instead. If a market cannot be resolved, the server returns suggestions rather than an error. Use everstrike_pairs for the full canonical list of market keys.

Available Tools

Prices & Markets

everstrike_ticker Live prices: last, mark and index price, plus 24-hour change and volume. Pass pairs when you have specific markets in mind to get every field for each one. Omit it to receive a compact summary — the full ticker spans 257 markets of ~50 fields each, so the summary is a deliberate view, not a truncation. everstrike_pairs Every tradable market with tick size, lot size, leverage caps, and contract type. No parameters. This is the canonical reference for market keys. everstrike_assets Supported assets with precision, deposit and withdrawal status, and network information. No parameters.

Market Depth & Activity

everstrike_depth Aggregated bid/ask depth for one market. everstrike_trades Recent public trades for one market. everstrike_ohlcv Candlestick history. The price parameter selects which price series to report:
start and end are Unix milliseconds. A seconds-based timestamp asks for candles from 1970 and returns an empty series without an error. Mark price is the default because on low-volume markets the last traded price can sit unchanged for hours, making a candle series misleading.
everstrike_funding Historical funding rates for perpetual markets.

Exchange

everstrike_status — Exchange-wide status: uptime, engine health, and maintenance windows. No parameters. everstrike_globals — Aggregate statistics: open interest, volume, and user counts. No parameters. everstrike_vault — Perpetual vault state: redemption rate, total earnings, and USD supply. No parameters.

Rate Limits

A response that exceeds the size limit is truncated with a note suggesting a narrower request. Truncation removes data from the end, so do not assume the information you need is present in a truncated response — narrow the request and call again.

Protocol Details

Because the server is stateless, a bare request works immediately — no initialize handshake is required before calling tools/list or tools/call. Sending an initialize is harmless, but it must be its own request: the transport rejects a JSON-RPC batch that contains initialize alongside other messages. Every request must include Accept: application/json, text/event-stream. Listing only one of the two types is rejected with a 406.