Is the Tesseralytics Hyperliquid Data MCP server down?

mcp-registry/dev.tesseralytics/hyperliquid-data · v0.1.0

As of 2026-10-26 18:06 UTC, the Tesseralytics Hyperliquid Data MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 17 minutes.

Hyperliquid perp market data for LLMs: OHLCV, funding, open interest, positioning & forecasts.

Point your MCP client at this streamable-http endpoint: https://tesseralytics.dev/mcp

Agent-readiness: B (82/100)

What to fix (4)

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.tesseralytics%2Fhyperliquid-data/fixes

{
  "name": "describe_dataset",
  "description": "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.",
  "inputSchema": {
    "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."
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_universe",
  "description": "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 on a Pro key) 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..50) only if you need the per-market counts.",
  "inputSchema": {
    "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..50) returns\nthat many markets, listed by name, alongside the summary."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "list_datasets",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.tesseralytics/hyperliquid-data"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.tesseralytics/hyperliquid-data"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~4,222 tokens).
• Tool names are unique and portable across clients.
• 99.94% uptime over 30 days.

Largest tool definitions

• screen_universe ~956 tokens
• query_cross_section ~856 tokens
• funding_divergence ~750 tokens
• get_universe ~562 tokens
• query_series ~514 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.tesseralytics%2Fhyperliquid-data.svg)](https://glimind.com/server/mcp-registry%2Fdev.tesseralytics%2Fhyperliquid-data?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fdev.tesseralytics%2Fhyperliquid-data?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.tesseralytics%2Fhyperliquid-data.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.tesseralytics%2Fhyperliquid-data.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.tesseralytics%2Fhyperliquid-data?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1631f28206db5c08…, first seen 2026-10-17, included at leaf 3414 of 74,609. Version history · verify what your client received.

Tools (9)

• describe_dataset
• funding_divergence
• get_universe
• list_datasets
• list_fields
• live_market
• query_cross_section
• query_series
• screen_universe

Compare: most reliable data servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Tesseralytics Hyperliquid Data MCP server down right now?

As of 2026-10-26 18:06 UTC, the Tesseralytics Hyperliquid Data MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 17 minutes.

How many tools does Tesseralytics Hyperliquid Data MCP server provide?

Tesseralytics Hyperliquid Data MCP server advertises 9 tools, including describe_dataset, funding_divergence, get_universe, list_datasets, list_fields.

How do I install Tesseralytics Hyperliquid Data MCP server?

Point your MCP client at this streamable-http endpoint: https://tesseralytics.dev/mcp

Is the Tesseralytics Hyperliquid Data MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Tesseralytics Hyperliquid Data MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.