_ registry / mcp http-sse · checked 3h ago

tessera-hyperliquid-data

https://tesseralytics.dev

Registry code: 3921c8e9a276fea4

api record

Cross-sectional market analytics for the Hyperliquid perp universe: rank, screen and compare every market on a completed day, follow one market's daily series, and read funding divergence from the majors. Start with list_fields to see the measurable fields, then query_cross_section, screen_universe, funding_divergence, get_universe or query_series. Browsing the catalog needs no key: list_datasets and describe_dataset cover the downloadable datasets, and list_fields the analytics vocabulary. Analytics require a free Tessera API key (get one at https://tesseralytics.dev) sent as `Authorization:…

endpoint
https://tesseralytics.dev/mcp
protocol
http-sse ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,515ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 9 tools
8 auth-required 1 never probed 8 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • describe_dataset auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "DatasetArg",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Dataset name, as returned by `list_datasets`."
    }
  },
  "description": "Which dataset's dictionary to return."
}
    arguments 15 lines
  • funding_divergence auth-required never probed

    Rank markets by how far their funding has diverged from a benchmark (default ETH) over a trailing window. metric=rate compares mean daily funding; metric=cum_funding_spread compares funding accumulated over the window. Returns the most diverged in each direction. Markets with no funding reading are excluded from both lists. Descriptive only.

    mcp-tool

    {
  "type": "object",
  "title": "DivergenceArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "coins": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": null,
      "nullable": true,
      "description": "Restrict to these markets."
    },
    "scope": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`crypto` (the default), `hip3`, or `all`."
    },
    "top_n": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "Markets per ranked list, 1..50. Defaults to 10."
    },
    "metric": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`rate` (the default) ranks each market's mean daily funding minus the\nbenchmark's; `cum_funding_spread` ranks funding accumulated over the\nwindow, high minus low, minus the benchmark's."
    },
    "benchmark": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The market whose funding is the yardstick. Defaults to ETH."
    },
    "window_days": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "Length of the trailing window in days, 1..365. Defaults to 7."
    }
  }
}
    arguments 50 lines
  • query_series auth-required never probed

    The daily series for one market or a few (max 10): one row per market per day over a trailing window, oldest first. Answers 'is this move backed by real flow' and 'how has positioning built up'. ending_day defaults to the last complete day. The whole answer is capped, so markets times window_days must stay inside the row cap; the response states the window it used.

    mcp-tool

    {
  "type": "object",
  "title": "SeriesArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "coins"
  ],
  "properties": {
    "coins": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The markets to return, 1..10."
    },
    "scope": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`crypto` (the default), `hip3`, or `all`."
    },
    "columns": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": null,
      "nullable": true,
      "description": "Fields to return per row, from `list_fields`. `day` and `coin` are\nalways included."
    },
    "ending_day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The last day to include, `YYYY-MM-DD` or `latest`."
    },
    "window_days": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "Length of the trailing window in days, 1..365. Defaults to 7."
    }
  }
}
    arguments 46 lines
  • screen_universe auth-required never probed

    Screen the whole market on ONE completed day with several conditions ANDed together. Conditions use op >, <, >=, <=, between, top_pct or bottom_pct; top_pct/bottom_pct are deciles of the markets you can see. 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.

    mcp-tool

    {
  "type": "object",
  "$defs": {
    "ConditionArg": {
      "type": "object",
      "required": [
        "column",
        "op",
        "value"
      ],
      "properties": {
        "op": {
          "type": "string",
          "description": "One of `>`, `<`, `>=`, `<=`, `between`, `top_pct`, `bottom_pct`.\n`top_pct`/`bottom_pct` keep the best/worst `value` percent of the\nmarkets you can see by that field."
        },
        "value": {
          "type": "number",
          "format": "double",
          "description": "The threshold. For `top_pct`/`bottom_pct` this is a percentage, e.g. 10\nfor the top decile."
        },
        "column": {
          "type": "string",
          "description": "The field to test, from `list_fields`."
        },
        "value2": {
          "type": "number",
          "format": "double",
          "default": null,
          "nullable": true,
          "description": "Required for `between`: the upper bound, inclusive."
        }
      },
      "description": "One condition of a screen."
    }
  },
  "title": "ScreenArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "conditions"
  ],
  "properties": {
    "day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The day to screen, `YYYY-MM-DD` or `latest`."
    },
    "coins": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": null,
      "nullable": true,
      "description": "Restrict to these markets."
    },
    "scope": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`crypto` (the default), `hip3`, or `all`."
    },
    "columns": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": null,
      "nullable": true,
      "description": "Fields to return per market, from `list_fields`."
    },
    "order_by": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The field to rank the matches by. Defaults to the day's traded notional."
    },
    "conditions": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/ConditionArg"
      },
      "description": "Conditions, all of which must hold. A market that does not report a\nfield never satisfies a condition on it."
    },
    "descending": {
      "type": "boolean",
      "default": null,
      "nullable": true,
      "description": "Rank largest first (the default)."
    },
    "max_results": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "How many markets to return, 1..50. Defaults to 25."
    },
    "min_usd_volume_7d_avg": {
      "type": "number",
      "format": "double",
      "default": null,
      "nullable": true,
      "description": "Drop markets below this average daily traded notional over the window."
    }
  }
}
    arguments 107 lines
  • list_datasets auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • live_market auth-required never probed

    What is happening right now: mark price, current hourly funding, open interest, 24-hour traded notional and premium for up to 25 markets, taken straight from the venue's public API and stamped with the moment it was read. Use this for 'now' questions; the daily tools answer completed days only.

    mcp-tool

    {
  "type": "object",
  "title": "LiveMarketArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "coins"
  ],
  "properties": {
    "coins": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The markets to snapshot, 1..25."
    }
  }
}
    arguments 17 lines
  • get_universe auth-required 3h ago

    The coverage picture: the last complete day, how many markets are in the universe for a scope, how much history sits behind them, and how densely it is populated. A compact SUMMARY by default — pass top_n (1..50) only if you need the per-market day counts.

    mcp-tool

    {
  "type": "object",
  "title": "UniverseArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The day to describe, `YYYY-MM-DD` or `latest`."
    },
    "scope": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`crypto` (the default), `hip3`, or `all`."
    },
    "top_n": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "Per-market detail is off by default; passing a value (1..50) returns\nthat many markets, listed by name, alongside the summary."
    }
  }
}
    arguments 27 lines
  • query_cross_section auth-required 3h ago

    Rank the whole market on ONE completed day: pick columns, an order_by field and top_n. Answers 'top markets by funding / open interest / returns on the latest day' and 'what percentile is BTC on open interest'. day defaults to the last complete day; scope defaults to crypto (HIP-3 markets track an underlying that closes, so their flow is not comparable); stat=percentile|zscore ranks within your visible markets; window_days recomputes the trailing-window fields; min_usd_volume_7d_avg keeps dust out of the ranking. Field names come from list_fields — never guess them, they are snake_case compound names; for a cut ('top decile by X') use screen_universe.

    mcp-tool

    {
  "type": "object",
  "title": "CrossSectionArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The day to rank, `YYYY-MM-DD`, or `latest` (the default: the most recent\ncomplete day)."
    },
    "stat": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`raw` (the default), `percentile`, or `zscore`. Percentile and z-score\nare ranked **within the markets your plan can see**, so they need a\nslice of at least four markets."
    },
    "coins": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": null,
      "nullable": true,
      "description": "Restrict to these markets. A market outside your plan's coverage is\nignored rather than widening the answer."
    },
    "scope": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`crypto` (the default), `hip3`, or `all`. Restricted markets track an\nunderlying that closes, so their flow is not comparable on a weekend."
    },
    "top_n": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "How many markets to return, 1..50. Defaults to 20."
    },
    "columns": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": null,
      "nullable": true,
      "description": "Fields to return per market, from `list_fields`. `coin` is always\nincluded. Defaults to price, traded notional and the day's return."
    },
    "order_by": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The field to rank by. Need not appear in `columns`. Defaults to the\nday's traded notional."
    },
    "descending": {
      "type": "boolean",
      "default": null,
      "nullable": true,
      "description": "Rank largest first (the default). Set false for the smallest."
    },
    "window_days": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "Recompute the trailing-window fields over this many days, 1..365\n(default 7). The response always states the window it used."
    },
    "min_usd_volume_7d_avg": {
      "type": "number",
      "format": "double",
      "default": null,
      "nullable": true,
      "description": "Drop markets whose average daily traded notional over the window is\nbelow this value, so dust cannot top a ranking."
    }
  }
}
    arguments 78 lines
  • list_fields unknown 3h ago

    Every field the query tools accept, each with its meaning, unit and whether it can be missing. 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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3921c8e9a276fea4/badge.svg)](https://brick.blue/agent/3921c8e9a276fea4)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.