Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Br0ski777/hyperliquid-data-x402Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/br0ski777/hyperliquid-data-x402/hyperliquid-data)<a href="https://agentmods.dev/mcp/br0ski777/hyperliquid-data-x402/hyperliquid-data"><img src="https://agentmods.dev/badge/mcp/br0ski777/hyperliquid-data-x402/hyperliquid-data/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/br0ski777/hyperliquid-data-x402/hyperliquid-data"><img src="https://agentmods.dev/badge/mcp/br0ski777/hyperliquid-data-x402/hyperliquid-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hyperliquid-data scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"hyperliquid-data": {
"url": "https://hyperliquid-data.api.klymax402.com/mcp",
"type": "sse"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A d7daeb4ffb85
hyperliquid-data is an MCP server published in the GitHub repository Br0ski777/hyperliquid-data-x402 (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
cerebrus-pulse-mcp
MCP server for Cerebrus Pulse — real-time crypto intelligence API for Hyperliquid perpetuals. Runs locally from the cerebrus-pulse-mcp Python package.
x402-api
DeFi data API for AI agents — pay-per-call via x402/USDC on Base. Runs locally from the @x402-api/mcp-server npm package. Needs 1 environment variable to run.
hl-portfolio
Hyperliquid account analysis: positions, PnL, fills, orders, funding. x402 pay-per-call. Remote server at hl-portfolio.api.klymax402.com.
liquidation-oracle
Real-time DeFi liquidation risk levels by protocol and asset. DeFiLlama-powered. x402. Remote server at liquidation-oracle.api.klymax402.com.
base-defi
Base chain DeFi yields — Aerodrome, Moonwell, APY, TVL, risk scores. x402. Remote server at base-defi.api.klymax402.com.
bridge-routes
Best cross-chain bridge routes with fees, time, providers. LI.FI-powered. x402. Remote server at bridge-routes.api.klymax402.com.