Skip to content

Hyperliquid Cross-Sectional Analytics (Tessera) MCP server

dev.tesseralytics/hyperliquid-datatesseralytics.devstreamable-httpv0.2.0Scanned

Rank, screen and compare the Hyperliquid perp universe on a completed day.

8 tools: 2 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server can do

The Hyperliquid Cross-Sectional Analytics (Tessera) MCP server is published by tesseralytics.dev, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: funding_divergence and screen_universe), but cannot delete data. 6 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 2Claude Code: ask
  • funding_divergenceRank markets by how far their funding has diverged from a benchmark (default ETH) over a trailing window.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Rank markets by how far their funding has diverged from a benchmark (default ETH) over a trailing window. Pick bar (1d, the default, or 1h for completed hours) to read completed days or completed hours. day defaults to the last complete interval. metric=rate compares mean funding over the window; metric=cum_funding_spread compares how far a market's cumulative funding level travelled inside the window (its high minus its low, so never negative) — that is not the funding the window accumulated: for that, read funding_paid from query_series and sum it. Returns the most diverged in each direction, each row with usd_volume_avg so a spread can be sized; pass min_usd_volume_7d_avg (USD/day) to exclude markets too illiquid to trade the divergence in. Markets with no funding reading are excluded from both lists. Descriptive only.

    Annotations the server declares

    • title: Funding divergence
    • readOnlyHint: true
  • screen_universeScreen the whole market on ONE completed interval with several conditions ANDed together.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Screen the whole market on ONE completed interval with several conditions ANDed together. Pick bar (1d, the default, or 1h for completed hours; the anonymous trial is screened at 1d). Conditions use op >, <, >=, <=, between, top_pct or bottom_pct; top_pct/bottom_pct are deciles of your eligible markets, and the liquidity floor (USD/day at either bar) is applied before the deciles so they are measured over the population you are choosing from. Answers 'top-decile funding with bottom-decile open-interest change' and 'open interest rising faster than volume'. A market that does not report a field never satisfies a condition on it.

    Annotations the server declares

    • title: Screen universe
    • readOnlyHint: true
Only reads 6Show 6 read-only tools
  • describe_datasetThe full dictionary for ONE downloadable dataset: description plus every column's type, nullability and plain-English meaning.No findings

    Why it is in this group

    • The name "describe_dataset" says "describe": a word for reading.
    Description, as the server wrote it
    The full dictionary for ONE downloadable dataset: description plus every column's type, nullability and plain-English meaning. Pass a name from list_datasets. Open — no key needed. For the fields the query tools accept, use list_fields.

    Annotations the server declares

    • title: Describe dataset
    • readOnlyHint: true
  • get_universeThe coverage picture: the last complete interval, how many markets are in the universe for a scope, how much history sits behind them, and how densely it is populated.No findings

    Why it is in this group

    • The name "get_universe" says "get": a word for reading.
    Description, as the server wrote it
    The coverage picture: the last complete interval, how many markets are in the universe for a scope, how much history sits behind them, and how densely it is populated. Pick bar (1d, the default, or 1h for completed hours) to describe completed days or completed hours. The range counts cover the last 7 days at bar: 1h (pass days, 1..30, to widen them) and the whole published range at bar: 1d. A compact SUMMARY by default — pass top_n (1..100, clamped) only if you need the per-market counts.

    Annotations the server declares

    • title: Get universe coverage
    • readOnlyHint: true
  • list_datasetsList the downloadable datasets: one-line summary, the plan required, and the month range available.No findings

    Why it is in this group

    • The name "list_datasets" says "list": a word for reading.
    Description, as the server wrote it
    List the downloadable datasets: one-line summary, the plan required, and the month range available. Open — no key needed. Then use describe_dataset for one dataset's columns, or list_fields for the fields the query tools accept.

    Annotations the server declares

    • title: List datasets
    • readOnlyHint: true
  • list_fieldsEvery field the query tools accept, each with its meaning, unit, whether it can be missing, and which bars (1d, 1h) it exists on.No findings

    Why it is in this group

    • The name "list_fields" says "list": a word for reading.
    Description, as the server wrote it
    Every field the query tools accept, each with its meaning, unit, whether it can be missing, and which bars (1d, 1h) it exists on. Open — no key needed. Call this before query_cross_section, screen_universe or query_series. Percentile, z-score and the top_pct/bottom_pct conditions rank within the markets your plan can see, so they need a wide slice.

    Annotations the server declares

    • title: List fields
    • readOnlyHint: true
  • query_cross_sectionRank the whole market on ONE completed interval: pick bar (1d, the default, or 1h for completed hours), columns, an order_by field and top_n.No findings

    Why it is in this group

    • The name "query_cross_section" says "query": a word for reading.
    Description, as the server wrote it
    Rank the whole market on ONE completed interval: pick bar (1d, the default, or 1h for completed hours), columns, an order_by field and top_n. Answers 'top markets by funding / open interest / returns on the latest day or hour' and 'what percentile is BTC on open interest'. day defaults to the last complete interval; scope defaults to crypto (HIP-3 markets track an underlying that closes, so their flow is not comparable); stat=percentile|zscore ranks within your eligible markets; min_usd_volume_7d_avg (USD/day at either bar) keeps dust out of the ranking and the ranking is computed after it. Field names come from list_fields — never guess them, they are snake_case compound names and each one lists the bars it exists on; for a cut ('top decile by X') use screen_universe.

    Annotations the server declares

    • title: Query cross-section
    • readOnlyHint: true
  • query_seriesThe series for one market or a few (max 10): one row per market per interval over a trailing window, ordered by interval then market.No findings

    Why it is in this group

    • The name "query_series" says "query": a word for reading.
    Description, as the server wrote it
    The series for one market or a few (max 10): one row per market per interval over a trailing window, ordered by interval then market. Pick bar (1d, the default, for one row per day, or 1h for one row per completed hour). Answers 'is this move backed by real flow' and 'how has positioning built up'. ending_day defaults to the last complete interval. The whole answer is capped, so markets times window_days (times 24 at bar 1h) must stay inside the row cap; the response states the window it used.

    Annotations the server declares

    • title: Query market series
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tesseralytics.dev/mcp: tools/list returned 8 tools to an anonymous client, including screen_universe (write), funding_divergence (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 3 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 removed, 5 changed.−1 removed~5 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 2.View diff
    • Tools that change things, listed without credentials: 3 to 2
  3. Tools9 changed.~9 changedView diff
  4. Tools5 changed.~5 changedView diff

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hyperliquid-data https://tesseralytics.dev/mcp
claude mcp add --transport http hyperliquid-data https://tesseralytics.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hyperliquid-data__get_universe",
      "mcp__hyperliquid-data__query_series",
      "mcp__hyperliquid-data__query_cross_section",
      "mcp__hyperliquid-data__list_fields",
      "mcp__hyperliquid-data__describe_dataset",
      "mcp__hyperliquid-data__list_datasets"
    ],
    "ask": [
      "mcp__hyperliquid-data__funding_divergence",
      "mcp__hyperliquid-data__screen_universe"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hyperliquid-data. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.tesseralytics/hyperliquid-data/verify?hash=fcd5d0f35414004db1b20a444827526278cace06e2d63f4cdea0d332851e1049" | jq -e '.changed == false'

Pinned hash fcd5d0f35414, from Nov 20, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.tesseralytics/hyperliquid-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.tesseralytics/hyperliquid-data
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.tesseralytics/hyperliquid-data.svg)](https://radar.anlyon.com/servers/dev.tesseralytics/hyperliquid-data)

Source: MCP Registry. Synced Nov 6, 2026, 15:17 UTC.

Hyperliquid Cross-Sectional Analytics (Tessera) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server have?

8 tools: 2 write, 6 read. funding_divergence, screen_universe, get_universe, query_series, query_cross_section, list_fields, describe_dataset and list_datasets.

Does the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hyperliquid Cross-Sectional Analytics (Tessera) MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.