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/johnsmithxy1mmm-sys/HyperliquidMCPWrote 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/johnsmithxy1mmm-sys/hyperliquidmcp/hypersignal-mcp)<a href="https://agentmods.dev/mcp/johnsmithxy1mmm-sys/hyperliquidmcp/hypersignal-mcp"><img src="https://agentmods.dev/badge/mcp/johnsmithxy1mmm-sys/hyperliquidmcp/hypersignal-mcp/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/johnsmithxy1mmm-sys/hyperliquidmcp/hypersignal-mcp"><img src="https://agentmods.dev/badge/mcp/johnsmithxy1mmm-sys/hyperliquidmcp/hypersignal-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hypersignal-mcp 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 8d 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
{ "hypersignal-mcp": { "command": "npx", "args": [ "-y", "hypersignal-mcp" ] } }
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.
- 8d ago First seen · 9 lines scan A 50f6d0173434
hypersignal-mcp is an MCP server published in the GitHub repository johnsmithxy1mmm-sys/HyperliquidMCP (1 stars, last pushed 18d 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
hyperliquid-data
Hyperliquid perp order book, prices, funding, OI, candles. x402 paid. Remote server at hyperliquid-data.api.klymax402.com.
mcp-pear
MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution. Runs locally from the @marvelcodes/mcp-pear npm package. Needs 5 environment variables to run.
hyperevm-mcp
Read-only Hyperliquid and HyperEVM data: yields, protocols, fees, markets, funding, depth. Runs locally from the @sand0vvv/hyperevm-mcp npm package.
defi-vaults
Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed. Remote server at mcp.philidor.io.
polskidegen-hl-tracker
Model Context Protocol server for Hyperliquid — read-only public data (positions, fills, funding, PnL) for any wallet address. Runs locally from the polskidegen-hl-tracker npm package.
vaultvision
Read-only Hyperliquid vault search, risk, drawdown, rankings, TVL, alerts, and comparisons. Remote server at vaultvision.tech.