perpdata

# PerpData MCP server

Normalized crypto perpetual-futures market data for agents and trading
systems: funding rates, open interest, liquidations and cross-venue spreads
from Bybit, OKX, Hyperliquid and Gate — Binance and Bitget rolling out — one schema,
five-minute snapshots, annualized `apr` on every rate so venues with
different funding intervals compare directly.

**Hosted server — nothing to install:**

```
https://api.perpdata.dev/mcp
```

```bash
claude mcp add --transport http perpdata https://api.perpdata.dev/mcp
```

Works with any MCP client speaking streamable HTTP (spec 2025-06-18).
Free tier needs no key or account; `initialize` and `tools/list` are never
metered, so wiring it up costs nothing.

## Tools

| Tool | Answers |
|---|---|
| `list_symbols` | What's tracked (BTC, ETH, SOL, … 25 majors) |
| `get_funding_rates` | Current funding per venue for a symbol, with apr + spread |
| `get_funding_history` | 5-minute snapshots, newest first |
| `get_funding_spreads` | Symbols ranked by cross-venue apr spread — the carry table |
| `get_open_interest` | OI per venue in base units + USD, cross-venue total |
| `get_liquidations` | Recent liquidation prints |

Schemas are deliberately terse: agent context is expensive, and a data tool
should spend your tokens on answers, not envelope.

## REST

The same data over plain JSON — see [docs](https://perpdata.dev/docs) and
[OpenAPI](https://api.perpdata.dev/openapi.json):

```bash
curl "https://api.perpdata.dev/v1/funding/current?symbol=BTC"
```

## Pricing

Free: 200 requests/day/IP, every tool and endpoint. Pro: $29/mo flat,
50k/day, commercial use allowed — [perpdata.dev](https://perpdata.dev).

## Why normalized matters

Hyperliquid funds hourly, Binance every eight hours; `1000PEPEUSDT` and
`kPEPE` are the same asset in different clothes; Gate sizes in quanto
contracts. PerpData resolves all of it so `apr` on one venue means the same
thing as `apr` on another. The alternative is maintaining six exchange
adapters yourself, forever.