HLWatch Hyperliquid Wallet Tracker
REMOTE · HLWATCH.DEANHIKI.WORKERS.DEV
Live Hyperliquid wallet positions, recent trades with PnL, and fill alerts to Discord/Telegram.
Available components
Last scanned (48 minutes ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 390 tokens (~130/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://hlwatch.deanhiki.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=deanhiki.workers.dev | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 58f858728bb6c6cc0ee1569063433f1c |
| SANs: deanhiki.workers.dev, *.deanhiki.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hlwatch.deanhiki.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hlwatch.deanhiki.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://hlwatch.deanhiki.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_wallet_positions ~77
Live Hyperliquid perp account snapshot for any wallet: account value, open positions (coin, side, size, entry, mark-based unrealized PnL, leverage, liquidation price), margin used and withdrawable. Public data, free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Hyperliquid wallet address 0x... (40 hex) |
No output schema declared.
No examples provided.
get_wallet_trades ~106
Recent Hyperliquid fills for a wallet (default last 24h, max 168h): direction (open/close long/short), coin, size, price, USD notional, realized PnL, fees, plus totals per coin. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Hyperliquid wallet address 0x... (40 hex) |
| hours | number | – | – |
| min_usd | number | – | Ignore fills smaller than this USD notional |
No output schema declared.
No examples provided.
start_wallet_alerts ~143
Push every new fill of up to 25 Hyperliquid wallets to a Discord webhook or Telegram bot within ~2 minutes. Free trial: 1 wallet for 3 days (no signup). Pro: 25 wallets, size filters, 5 USDC/month (key HW-... from https://hlwatch.deanhiki.workers.dev/#pro).
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | – |
| chat_id | string | – | Telegram chat_id (Telegram only) |
| min_usd | number | – | – |
| pro_key | string | – | – |
| webhook | string | yes | Discord webhook URL or https://api.telegram.org/bot<token>/sendMessage |
No output schema declared.
No examples provided.
How do I install the HLWatch Hyperliquid Wallet Tracker MCP server?
HLWatch Hyperliquid Wallet Tracker is a hosted endpoint at https://hlwatch.deanhiki.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hlwatch.deanhiki.workers.dev
claude mcp add --transport http dev-workers-deanhiki-hlwatch-hyperliquid-wallets 'https://hlwatch.deanhiki.workers.dev/mcp'
What is the HLWatch Hyperliquid Wallet Tracker MCP server?
HLWatch Hyperliquid Wallet Tracker is an MCP server listed in the public MCP registry as dev.workers.deanhiki.hlwatch/hyperliquid-wallets. Live Hyperliquid wallet positions, recent trades with PnL, and fill alerts to Discord/Telegram. This page covers its hosted endpoint (https://hlwatch.deanhiki.workers.dev/mcp).
Is the HLWatch Hyperliquid Wallet Tracker MCP server safe to use?
HLWatch Hyperliquid Wallet Tracker scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HLWatch Hyperliquid Wallet Tracker MCP server expose?
HLWatch Hyperliquid Wallet Tracker exposes 3 tools: get_wallet_positions, get_wallet_trades, start_wallet_alerts. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Does the HLWatch Hyperliquid Wallet Tracker MCP server require authentication?
No. We connected to HLWatch Hyperliquid Wallet Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HLWatch Hyperliquid Wallet Tracker MCP server still maintained?
HLWatch Hyperliquid Wallet Tracker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.