_ registry / mcp http-sse · checked 2h 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 interval, follow one market's series, and read funding divergence from the majors. Every analytical tool takes bar: 1d (the default) for completed UTC days, or bar: 1h for completed UTC hours, and each answer states which it answered and the exact interval it used. Start with list_fields to see the measurable fields and the bars each one exists on, then query_cross_section, screen_universe, funding_divergence, get_universe or query_series. Browsing the catalog needs no key:…

endpoint
https://tesseralytics.dev/mcp
protocol
http-sse ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tessera-hyperliquid-data live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is tessera-hyperliquid-data free to use?
Yes — the hub reached it with no key and no payment.
What tools does tessera-hyperliquid-data have?
9 tools: describe_dataset, list_datasets, screen_universe, query_series, live_market, get_universe, list_fields, query_cross_section, ….
Is tessera-hyperliquid-data safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 98.9%· all time 98.9%

latency
1,568ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 279 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain prices & market data
used for
  • rank hyperliquid markets on an interval
  • screen perp markets by conditions
  • compare funding divergence
  • get live market state
  • download market datasets
takes → gives
text → data
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
4 open 5 never probed 4 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.

  • get_universe reads open 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "UniverseArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "bar": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`1d` (the default) for completed UTC days, `1h` for completed UTC hours.\nAn interval, at either grain, is stamped by the instant it **closes** —\nan hourly `…T09:00:00Z` is the hour that ended at 09:00."
    },
    "day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The day or hour to describe: `YYYY-MM-DD` or `latest` at `bar: 1d`, a\ncompleted `YYYY-MM-DDTHH:00:00Z` (the hour that *ended* there) or\n`latest` at `bar: 1h`."
    },
    "days": {
      "type": "integer",
      "format": "uint",
      "default": null,
      "minimum": 0,
      "nullable": true,
      "description": "How many days of completed intervals the range counts cover, 1..30.\nDefaults to 7 at `bar: 1h` — the hourly source publishes one object per\ncompleted hour, so an unbounded inventory would open every hour ever\npublished — and to the whole published range at `bar: 1d`, whose source\nis one object per month. The window the counts actually covered is\n`interval_start`..`interval_end`, and `notes` says when it was bounded."
    },
    "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..100, clamped)\nreturns that many markets, listed by name, alongside the summary."
    }
  }
}
    arguments 41 lines
  • list_fields reads open 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • query_cross_section reads open 5h ago

    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; window_days recomputes the trailing-window fields; 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.

    mcp-tool

    {
  "type": "object",
  "title": "CrossSectionArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "bar": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`1d` (the default) for completed UTC days, `1h` for completed UTC hours.\nAn interval, at either grain, is stamped by the instant it **closes** —\nan hourly `…T09:00:00Z` is the hour that ended at 09:00."
    },
    "day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The day or hour to rank. For `bar: 1d`, `YYYY-MM-DD` or `latest` (the\ndefault: the most recent complete day). For `bar: 1h`, a completed hour\nas `YYYY-MM-DDTHH:00:00Z` — the hour that *ended* at that instant — or\n`latest`."
    },
    "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..100 (values outside are clamped to the\nnearest bound and the response says so). 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 interval's return."
    },
    "order_by": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The field to rank by. Need not appear in `columns`. Defaults to the\ninterval'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 trailing\nwindow is below this value, in USD/day at either bar — a floor chosen at\n`1d` means the same thing at `1h` — so dust cannot top a ranking."
    }
  }
}
    arguments 84 lines
  • funding_divergence reads open 2h ago

    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, which is funding_paid_7d (or funding_rate_7d_avg times the window's completed-interval count). Returns the most diverged in each direction, each row with usd_volume_7d_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.

    mcp-tool

    {
  "type": "object",
  "title": "DivergenceArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "bar": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`1d` (the default) for completed UTC days, `1h` for completed UTC hours.\nAn interval, at either grain, is stamped by the instant it **closes** —\nan hourly `…T09:00:00Z` is the hour that ended at 09:00."
    },
    "day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The day or hour to rank as of: `YYYY-MM-DD` or `latest` at `bar: 1d`, a\ncompleted `YYYY-MM-DDTHH:00:00Z` (the hour that *ended* there) or `latest`\nat `bar: 1h`."
    },
    "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..100 (values outside are clamped to the\nnearest bound and the response says so). Defaults to 10."
    },
    "metric": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`rate` (the default) ranks each market's mean funding over the window\nminus the benchmark's; `cum_funding_spread` ranks the **spread of the\ncumulative funding level** over the window — its high minus its low, so\nalways non-negative — minus the benchmark's. That is not the funding the\nwindow accumulated: `cum_funding` is a running total, so a market whose\nlevel retraced has a large spread and a *negative* accumulation (and one\nthat reversed inside the window has a spread several times its true\naccumulation). Measured 2026-10-13 over 34 markets and the trailing 168\nhours, the expression below reproduced the served value exactly, while\n`SUM(funding_paid)` over the same window disagreed in sign for 11 of\nthem (TRX +0.00440 vs −0.00445) and by up to 100× (CASHCAT 0.2050 vs\n0.0020). The accumulation is `funding_paid_7d`, or equivalently\n`funding_rate_7d_avg` × the window's completed-interval count — 7\nintervals at the daily grain and 168 at the hourly one."
    },
    "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."
    },
    "min_usd_volume_7d_avg": {
      "type": "number",
      "format": "double",
      "default": null,
      "nullable": true,
      "description": "Drop markets whose average **daily** traded notional over the divergence\nwindow is below this value, in USD/day at either bar. Each row carries\nthat figure as `usd_volume_7d_avg`, so the floor decides which spreads\nare tradeable rather than which are largest."
    }
  }
}
    arguments 69 lines
  • describe_dataset reads unknown 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
  • list_datasets reads unknown 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
  • screen_universe reads unknown 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$defs": {
    "ConditionArg": {
      "type": "object",
      "required": [
        "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",
          "default": null,
          "nullable": true,
          "description": "The field to test, from `list_fields`. Accepted under either name —\n`field`, which is what every other argument on this surface calls it, or\nits original `column`. Validated as present rather than required by the\nschema, so a condition that names no field is rejected by name below\ninstead of by a deserializer message no caller can act on."
        },
        "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": {
    "bar": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`1d` (the default) for completed UTC days, `1h` for completed UTC hours.\nAn interval, at either grain, is stamped by the instant it **closes** —\nan hourly `…T09:00:00Z` is the hour that ended at 09:00."
    },
    "day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The day or hour to screen: `YYYY-MM-DD` or `latest` at `bar: 1d`, a\ncompleted `YYYY-MM-DDTHH:00:00Z` (the hour that *ended* there) or\n`latest` at `bar: 1h`."
    },
    "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 interval's traded\nnotional."
    },
    "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..100 (values outside are clamped to the\nnearest bound and the response says so). Defaults to 25."
    },
    "min_usd_volume_7d_avg": {
      "type": "number",
      "format": "double",
      "default": null,
      "nullable": true,
      "description": "Drop markets whose average **daily** traded notional over the trailing\nwindow is below this value, in USD/day at either bar — a floor chosen at\n`1d` means the same thing at `1h`."
    }
  }
}
    arguments 114 lines
  • query_series reads unknown 16h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "SeriesArgs",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "coins"
  ],
  "properties": {
    "bar": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "`1d` (the default) for completed UTC days, `1h` for completed UTC hours.\nAn interval, at either grain, is stamped by the instant it **closes** —\nan hourly `…T09:00:00Z` is the hour that ended at 09:00."
    },
    "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`. The interval column\n(`day` at 1d, `hour` at 1h) and `coin` are always included."
    },
    "ending_day": {
      "type": "string",
      "default": null,
      "nullable": true,
      "description": "The last interval to include: `YYYY-MM-DD` or `latest` at `bar: 1d`, a\ncompleted `YYYY-MM-DDTHH:00:00Z` (the hour that *ended* there) or\n`latest` at `bar: 1h`."
    },
    "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. At\n`bar: 1h` one window day is 24 hourly rows."
    }
  }
}
    arguments 52 lines
  • live_market reads unknown 28h ago

    What is happening right now: mark price, current hourly funding, open interest (one-sided — counted once per contract, half of the both-sides figure Hyperliquid's own UI shows, so it is directly comparable with the oi_usd column the bar tools return), 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 bar=1d and bar=1h tools answer completed intervals 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
_ 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3921c8e9a276fea4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3921c8e9a276fea4/claim. Over MCP: the claim_endpoint tool.

_ 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?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ 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.