Is the Br0ski777 Hl Spot MCP server down?

mcp-registry/io.github.br0ski777/hl-spot · v1.0.0

Also listed as glama/br0ski777/hl-spot

down
Last checked 2026-10-23 19:48 UTC · handshake 393ms

As of 2026-10-23 19:48 UTC, the Br0ski777 Hl Spot MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
0%
checks observed
5
outages (90d)
3
tools
3

Hyperliquid spot tokens, prices, volume, wallet balances. 454 tokens. x402 micropayment.

Point your MCP client at this streamable-http endpoint: https://hl-spot.api.klymax402.com/mcp

Agent-readiness: C (75/100)

C (75/100): 1 error(s), 1 warning(s) across 3 tool(s); ~669 tokens of tool definitions.
Scores higher than 10% of 15,762 MCP servers Glimind has audited.
Its tool list costs an agent ~669 tokens per session — lighter than 85% of servers.
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (3)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: hyperliquid_get_spot_balances, hyperliquid_get_spot_markets, hyperliquid_list_spot_tokens

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 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%2Fio.github.br0ski777%2Fhl-spot/fixes

hyperliquid_get_spot_balances 1 change
{
  "name": "hyperliquid_get_spot_balances",
  "description": "Use this when you need to check spot token balances for a specific wallet address on Hyperliquid L1 DEX. Returns all non-zero spot token holdings with available and held (in-order) amounts.\n\nReturns for each balance:\n1. coin: token symbol\n2. token: token index in spot registry\n3. total: total balance (hold + available) as string\n4. hold: amount currently held in open orders\n5. available: amount available for trading or withdrawal\n6. entryNtl: entry notional value in USDC\n\nInput: wallet address (",
  "inputSchema": {
    "type": "object",
    "required": [
      "address"
    ],
    "properties": {
      "address": {
        "type": "string",
        "description": "Wallet address in 0x format (42 characters). Example: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
hyperliquid_get_spot_markets 1 change
{
  "name": "hyperliquid_get_spot_markets",
  "description": "Use this when you need live spot market data from Hyperliquid DEX: prices, 24h volume, and trading activity for all spot pairs. Returns merged token metadata + real-time market context for every active spot market.\n\nReturns for each market:\n1. name: token name (e.g. \"PURR/USDC\")\n2. coin: base token symbol\n3. tokenId: unique token identifier\n4. markPx: current mark/mid price in USDC\n5. midPx: mid price between best bid and ask\n6. prevDayPx: previous day closing price\n7. dayNtlVlm: 24h notional vo",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "sort": {
        "enum": [
          "volume",
          "change",
          "name"
        ],
        "type": "string",
        "description": "Sort order for results. 'volume' = highest 24h volume first (default), 'change' = biggest price movers first, 'name' = alphabetical."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
hyperliquid_list_spot_tokens 1 change
{
  "name": "hyperliquid_list_spot_tokens",
  "description": "Use this when you need to list or search spot tokens available on Hyperliquid L1 DEX. Returns all 454 spot tokens with full metadata including token name, symbol, tokenId, index, decimals, and wei conversion factors.\n\nReturns for each token:\n1. name: token display name (e.g. \"PURR\", \"HFUN\")\n2. tokenId: unique hex token identifier on Hyperliquid\n3. index: integer index in the spot meta registry\n4. decimals: token decimal precision (szDecimals)\n5. weiDecimals: wei-level decimal precision for raw a",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "search": {
        "type": "string",
        "description": "Optional filter: search tokens by name or symbol (case-insensitive substring match). Omit to return all 454 tokens."
      }
    }
  },
  "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/io.github.br0ski777/hl-spot"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.br0ski777/hl-spot"}) over MCP.

Passed

Largest tool definitions

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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Fhl-spot.svg)](https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Fhl-spot?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Fhl-spot?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Fhl-spot.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Fhl-spot.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Fhl-spot?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:a42573945d251351…, first seen 2026-10-17, included at leaf 12772 of 75,126. Version history · verify what your client received.

Working alternatives

Tools (3)

Compare: most reliable finance servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Br0ski777 Hl Spot MCP server down right now?

As of 2026-10-23 19:48 UTC, the Br0ski777 Hl Spot MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Br0ski777 Hl Spot MCP server provide?

Br0ski777 Hl Spot MCP server advertises 3 tools, including hyperliquid_get_spot_balances, hyperliquid_get_spot_markets, hyperliquid_list_spot_tokens.

How do I install Br0ski777 Hl Spot MCP server?

Point your MCP client at this streamable-http endpoint: https://hl-spot.api.klymax402.com/mcp

Is the Br0ski777 Hl Spot MCP server safe to connect to an AI agent?

Glimind scanned all 3 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 Br0ski777 Hl Spot 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.

Feedback
Help us improve