Hyperliquid Market Data — OHLCV, Funding Rates & Positioning (Tessera)
Server Details
Hyperliquid perp market data for LLMs: OHLCV, funding, open interest, positioning & forecasts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 6 of 6 tools scored. Lowest: 3.8/5.
Each tool has a clearly distinct purpose: metadata (describe_dataset), discovery (list_datasets, list_partitions), data access (read_dataset, query_cross_section), and bulk download (get_download_url). No overlaps.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., describe_dataset, get_download_url, list_datasets). Predictable and easy to use.
With 6 tools, the server is well-scoped. It covers all necessary operations for a read-only market data server without unnecessary redundancy.
The tool set provides full lifecycle for data access: discovery, metadata retrieval, row reading, bulk download, and specialized cross-section queries. No obvious gaps for the stated purpose.
Available Tools
6 toolsdescribe_datasetInspect
Get the full data dictionary for one dataset: prose plus every column's type, nullability and plain-English meaning. Use before read_dataset to choose columns.
| Name | Required | Description | Default |
|---|---|---|---|
| asset | Yes | Dataset name, e.g. `gold_positioning_funding_factors_1d`. |
Output Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | Dataset name / asset key, e.g. `gold_ohlcv_1m`. |
| note | No | Optional "how to use this" callout. |
| tier | Yes | Display tier: `free` or `pro`. Re-derived from `policy.rs` on read, so it always matches actual entitlement regardless of the on-disk value. |
| title | Yes | Human-friendly title, e.g. "Order-flow OHLCV (1-minute)". |
| cadence | Yes | Granularity + partitioning, e.g. "1-minute bars, partitioned per (coin, month)". |
| summary | Yes | One-line intuitive summary — the catalog card. |
| category | Yes | Presentation category, e.g. `raw-tiles` or `forecast-layer`. |
| keywords | No | Per-dataset discovery keywords (schema.org keywords on the web). |
| temporal | No | Machine-readable timestamp/interval contract: what the label marks and how to join without leaking the future. Defaulted so snapshots predating the field still deserialize. |
| use_case | No | One-line "what you'd use it for" (buyer-intent) copy. |
| seo_title | No | Keyword-first SEO title tag (web `<title>`). Defaulted so older snapshots without the field still deserialize. |
| description | Yes | Longer prose — the dictionary page header. |
| column_count | Yes | Number of documented columns. |
| column_groups | Yes | Columns, grouped for presentation, in schema order. |
| direct_answer | No | 40-60 word keyword-first lead answer — the definitional "what is this" blurb, and the strongest AI-citation extraction target. Defaulted for forward/backward compatibility with snapshots predating the field. |
get_download_urlInspect
Return a short-lived presigned URL to download the full parquet for one (asset, coin, month) partition. Use for bulk access beyond read_dataset's row cap.
| Name | Required | Description | Default |
|---|---|---|---|
| coin | No | Coin symbol, e.g. `BTC`. Omit for market-wide datasets that have no coin dimension. | |
| asset | Yes | ||
| month | Yes | Partition month, `YYYY-MM`. |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | Presigned Tigris URL for the full parquet partition. |
| expires_at | Yes | RFC3339 expiry. |
list_datasetsInspect
List the available Tessera Analytics gold datasets with summaries and the plan (free/pro) each requires. Call first to discover what's available.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| datasets | Yes | |
| your_tier | Yes | The caller's own plan (`free` or `pro`). Datasets whose `tier` is `pro` while this is `free` are visible for discovery but require an upgrade to read. |
| generated_at | Yes |
list_partitionsInspect
List a dataset's (coin, month) partitions the caller's plan can read. Defaults to a compact SUMMARY (coin/month counts, month range, totals) — pass summary=false to enumerate (paginated via limit/offset). Filter with coin and/or month. Use to choose a valid coin/month for read_dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| coin | No | Optional: only partitions for this coin, e.g. `BTC`. | |
| asset | Yes | Dataset name, e.g. `gold_funding_1h`. | |
| limit | No | Full mode only (`summary=false`): max partitions to return (clamped to 1000). Defaults to 200. | |
| month | No | Optional: only partitions for this month, `YYYY-MM`. | |
| offset | No | Full mode only (`summary=false`): partitions to skip, for pagination. Defaults to 0; pass the previous response's `next_offset` for the next page. | |
| summary | No | Return compact coverage stats (coin/month counts, range, totals) instead of every `(coin, month)` row. Defaults to **true** — the full cross-product is hundreds of rows for some datasets. Set `false` to enumerate (paginated via `limit`/`offset`). |
Output Schema
| Name | Required | Description |
|---|---|---|
| note | No | Set when the dataset exists but requires a plan the caller doesn't have. |
| asset | Yes | |
| summary | No | Present in summary mode (the default): compact coverage stats. |
| your_tier | Yes | |
| partitions | Yes | Present in full mode (`summary=false`): this page of partitions. Empty in summary mode. |
| next_offset | No | Full mode only: pass as `offset` to fetch the next page, or null when the listing is exhausted. |
| generated_at | Yes | |
| total_matching | Yes | Full mode only: total partitions matching the filter, before pagination. |
query_cross_sectionInspect
Rank all coins for one day of a daily cross-section dataset (one row per coin per day, e.g. gold_positioning_funding_factors_1d) in a single call. Pass order_by (a numeric column), day (YYYY-MM-DD or "latest"), optional top_n (default 20), descending (default true), columns, and coins. Replaces fanning out read_dataset per coin. For a single coin's series use read_dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| day | Yes | UTC day to rank, `YYYY-MM-DD`, or `"latest"` for the newest available day. | |
| asset | Yes | Dataset name. Must be a daily coin cross-section (one row per coin per `day`), e.g. `gold_positioning_funding_factors_1d`. | |
| coins | No | Optional: restrict to these coins. Coins outside the caller's plan are dropped. Omit to rank every coin the plan allows. | |
| top_n | No | Max coins to return (clamped to 1000). Defaults to 20. | |
| columns | No | Extra columns to include per row (besides `coin`, `day`, and `order_by`). Omit to return every column. | |
| order_by | Yes | Numeric column to rank coins by, e.g. a `factor_*` column. Call `describe_dataset` to see the options. | |
| descending | No | Sort direction. Defaults to true — highest `order_by` first. |
Output Schema
| Name | Required | Description |
|---|---|---|
| day | Yes | The day actually ranked (resolved when `day="latest"`), `YYYY-MM-DD`. |
| note | No | Advisories: latest-day resolution, coins with no row that day (coverage varies by day), coins excluded for a null/non-numeric `order_by`, and any partitions skipped on a read error. |
| rows | Yes | One object per coin, ranked; each includes `coin`, `day`, `order_by` and any requested `columns`. |
| asset | Yes | |
| columns | Yes | Columns present in each returned row. |
| order_by | Yes | |
| coin_count | Yes | Number of coins ranked (rows returned). |
| descending | Yes |
read_datasetInspect
Read actual data rows from one (asset, coin, month) partition. Defaults to the latest 200 rows. Pass columns to limit width and limit (max 1000) to limit rows — a partition can be tens of thousands of rows. For a whole partition use get_download_url.
| Name | Required | Description | Default |
|---|---|---|---|
| coin | No | Coin symbol, e.g. `BTC`. Omit for market-wide datasets (e.g. `gold_wallet_flow_1mo`) that have no coin dimension. | |
| asset | Yes | Dataset name, e.g. `gold_positioning_funding_factors_1d`. | |
| limit | No | Max rows to return (clamped to 1000). Defaults to the latest 200. | |
| month | Yes | Partition month, `YYYY-MM`. | |
| order | No | Which end of the partition to read. `latest` (default) returns the most recent rows — usually what you want for a "what's the current…" question. | |
| columns | No | Columns to return. Strongly recommended — omitting returns every column, which is wide for some datasets. Use `describe_dataset` to see columns. |
Output Schema
| Name | Required | Description |
|---|---|---|
| coin | No | Coin symbol; absent for market-wide datasets. |
| note | No | Guidance when the result was capped, or other advisories. |
| rows | Yes | One JSON object per row. |
| asset | Yes | |
| month | Yes | |
| columns | Yes | The columns actually returned, in order. |
| row_count | Yes | |
| truncated | Yes | True when `total_rows_in_partition` exceeds the rows returned. |
| total_rows_in_partition | Yes | Total rows in the partition (before the row cap / limit). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!