MCP servers observed by Lowdown
io.github.ironflowsh/hyperliquid MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 54 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ironflowsh/hyperliquid
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ironflowsh/hyperliquid?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, server version changed
- 2026-11-13: input or output schemas changed, descriptions changed, server version changed
What tools does it list?
54 tools on 2026-11-16:
create_ironboxcreate_liquidation_alertdelete_ironboxdelete_liquidation_alertdescribe_dataget_auto_deleveragingget_box_activityget_candlesget_cohort_addressesget_early_moversget_fillsget_funding_ratesget_funding_statsget_ironboxget_liquidation_levelsget_liquidation_mapget_liquidation_summaryget_liquidationsget_mark_pricesget_market_leadersget_market_top_walletsget_markets_snapshotget_open_interestget_open_interest_changesget_outcome_marketsget_pnl_leaderboardget_positions_atget_premiumget_priceget_recent_tradesget_statusget_status_historyget_status_metricsget_top_tradersget_trader_profileget_user_fundingget_user_ledgerget_user_maker_takerget_user_pnl_seriesget_user_stateget_user_summaryget_vault_leaderboardget_vault_operationsget_wallet_behaviorget_wallet_labelslist_box_strategieslist_cohortslist_ironboxeslist_liquidation_alertslist_marketsrun_querystart_box_strategystop_box_strategytest_liquidation_alert
MCP Registry declaration
- Registry name:
io.github.ironflowsh/hyperliquid - Declared version: 0.20.1
- Status: active
- Declared hosts:
mcp.ironflow.sh
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.ironflowsh/hyperliquid", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ironflowsh/hyperliquid?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.ironflowsh/hyperliquid -- npx -y @ironflowsh/mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).