hyperliquid-whalealert-mcp

by kukapay

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Related Servers

Alternatives to hyperliquid-whalealert-mcp

No user-submitted related servers found.

Related Servers

hyperliquid-info-mcp
Cryptocurrency Finance Blockchain
kukapay
A
license
A
quality
F
maintenance
An MCP server that provides real-time data and insights from the Hyperliquid perp DEX for use in bots, dashboards, and analytics.
Updated a year ago (2025-05-31 08:00 UTC)
17
30
MIT
hypersignal
Cryptocurrency Finance Blockchain
johnsmithxy1mmm-sys
A
license
A
quality
A
maintenance
Monetized MCP server for Hyperliquid whale/funding/risk analytics + signals;
Updated a month ago (2026-08-21 07:08 UTC)
17
1
MIT
whale-insights
Blockchain Code Analysis Finance
cryptowhaleinsights-ux
A
license
A
quality
B
maintenance
Real-time crypto whale intelligence MCP server with 55 tools across 14 blockchains. Free, no auth required.
Updated a month ago (2026-09-03 08:45 UTC)
56
1
MIT
whale-tracker-mcp
Cryptocurrency Monitoring Data Platforms
kukapay
A
license
Not graded
quality
D
maintenance
A mcp server for tracking cryptocurrency whale transactions.
Updated a year ago (2025-05-07 17:24 UTC)
56
MIT
Hyperliquid MCP Server
Cryptocurrency Finance Blockchain
samimiair
F
license
Not graded
quality
C
maintenance
MCP server for Hyperliquid perpetual DEX with 48 tools for trading, monitoring, risk management, and security. Enables real-time market data, order management, risk validation, and automated trading strategies.
Updated 4 months ago (2026-06-08 21:03 UTC)
-
hyperliquid-mcp
Cryptocurrency Finance
tomarsachin2271
A
license
Not graded
quality
D
maintenance
MCP server that allows querying Hyperliquid open positions and unrealized PnL for any wallet address.
Updated 9 months ago (2025-12-26 05:17 UTC)
7 npm
MIT

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored 2026-04-18 10:05 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching whale alerts, making it distinct by default.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (get_whale_alerts), which is consistent and predictable. Since there are no other tools to compare against, naming is inherently consistent.

Tool Count2/5

A single tool is too few for the server's apparent purpose of monitoring whale alerts, as it lacks operations like filtering, subscribing, or historical queries. This minimal scope limits functionality and may cause agent failures due to incomplete coverage.

Completeness2/5

The tool surface is severely incomplete for a whale alert system, offering only fetching recent alerts without capabilities such as filtering by criteria, accessing historical data, or managing alerts. This creates significant gaps that will hinder agent workflows.