Tessera Analytics
Model Context Protocol

Tessera Analytics — the Hyperliquid MCP server

Point Claude — or any MCP client — at the Tessera Hyperliquid MCP server and ask market questions in plain language. Nine tools: discover the catalog and the field vocabulary, then rank the cross-section, screen on several conditions, measure funding divergence, pull per-coin series and read the live market — all authed with your API key.

Get an API key Browse the catalog

What it is

The Model Context Protocol lets an AI assistant call external tools. Our hosted Hyperliquid MCP server exposes Tessera Analytics as a small set of market-intelligence tools, so instead of writing download scripts you can just ask — "what's BTC trading at right now?" or "which coins are most crowded on funding?" — and the model calls the right tool and reasons over the result. It's a single hosted endpoint (https://tesseralytics.dev/mcp), authed with the same API key you use for the REST API.

Installation

First, create an API key on your account page. Then wire it into your client — replace YOUR_TESSERA_API_KEY with your key.

Claude Code

One command — native streamable-HTTP transport with a header.

claude mcp add --transport http tessera https://tesseralytics.dev/mcp \
  --header "Authorization: Bearer $TESSERA_API_KEY"
Clients with native header auth

For MCP clients that accept a remote URL plus custom headers, add this to your MCP config.

{
  "mcpServers": {
    "tessera": {
      "type": "http",
      "url": "https://tesseralytics.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TESSERA_API_KEY"
      }
    }
  }
}
Claude Desktop (via mcp-remote)

Some desktop clients don't yet send custom headers to remote servers. The mcp-remote bridge proxies the connection and injects your key. Add this to claude_desktop_config.json, then restart the app.

{
  "mcpServers": {
    "tessera": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://tesseralytics.dev/mcp",
        "--header", "Authorization: Bearer ${TESSERA_API_KEY}"
      ],
      "env": {
        "TESSERA_API_KEY": "YOUR_TESSERA_API_KEY"
      }
    }
  }
}

Tools

Nine tools: three open discovery tools, six keyed analytics tools. Discovery works without a key; the analytics tools take your API key and see only your plan's slice of the market.

Open — no API key

Discovery. These answer before you sign in, so an assistant can learn the vocabulary first.

Tool Arguments What it answers
list_datasets — Every dataset you can access, with a one-line summary and the plan it needs.
describe_dataset dataset One dataset in full: each column’s type, nullability and plain-English meaning.
list_fields — Every field the query tools accept, with its meaning and its unit.

Keyed — API key required

Analytics. Your key hands the model your plan’s slice of the market; it can’t widen or remove it.

Tool Arguments What it answers
query_cross_section day (YYYY-MM-DD | latest), columns[], order_by, top_n, scope? Rank the whole market on one complete day — top coins by funding, returns, volume and more. Add stat? for a percentile or z-score instead of the raw value.
screen_universe day (YYYY-MM-DD | latest), conditions[], columns[], max_results, scope? Screen on several conditions at once — e.g. top-decile funding with bottom-decile open-interest change.
funding_divergence window_days, benchmark? (default ETH), metric?, top_n, scope? Which coins’ funding is diverging from a benchmark over a trailing window.
get_universe day? (YYYY-MM-DD | latest), summary? The coverage picture: last complete day, coin counts by scope, row density and completeness flags.
query_series coins[] (≤10), window_days, columns[], ending_day? (YYYY-MM-DD | latest) A trailing daily series for one or a few coins — is this move backed by real flow?
live_market coins[] (≤25) Right now: price, funding, open interest, 24-hour volume and premium. The only “now” tool.

How fresh the data is

The daily tools serve complete UTC days only — a day is available once it has closed, and the day still in progress is never served. Leave the day out or pass latest and the tool resolves to the last complete day, telling you in the response when it substituted; ask for a day before or after the covered range and you get an explicit error naming the range rather than silent zeros.

live_market is the only now tool — price, funding and open interest as of the moment you ask. Every keyed response states the day it covers, the market scope it ranked, and how many coins the statistics were computed over.

Rankings and screens are computed within the coins you can see, so they need a wide enough slice to be meaningful — a one-coin slice is refused instead of returning a hollow percentile.

Fields

Field names, meanings and units are not something you memorise: call list_fields (or ask for the vocabulary in plain language) and the model gets every column the query tools accept, each with a plain-English meaning and its unit. Discovery is free — pass those names straight into columns, a screen condition, or order_by.

Example prompts

Once connected, drive it in natural language — each question maps to one tool. A few things to try:

Free vs Pro

Any valid API key can use the MCP server. A free key sees BTC, ETH, SOL and HYPE over a trailing 30-day history — enough to explore the data end-to-end.

Pro ($29/mo) unlocks full history, every market (incl. HIP-3), and the full funding and positioning record. Discovery tools show the whole catalog regardless of plan; asking for a slice outside your plan returns a clear "requires Pro" message. See Pricing.