Reins
OfficialRelated Servers
Alternatives to Reins
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely trade on Hyperliquid perpetual exchange, including order placement, position management, market data retrieval, and vault operations via natural language.16 PyPI23MIT
- AlicenseAqualityCmaintenanceEnables natural language control of Hyperliquid perpetual futures, including querying positions, prices, orderbook, and executing trades like market and limit orders, all from MCP-compatible clients.13MIT
- AlicenseAqualityBmaintenanceAn MCP server that lets AI agents read Hyperliquid perpetual futures market data and their own account state, then place and cancel orders, adjust leverage, move USDC from spot to perp, and convert stablecoins to USDC. It holds no credentials and never contacts the exchange, routing every request through a runtime that enforces caps and signs server-side.9Apache 2.0

AlgoVesta MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceConnects AI assistants to 16 crypto exchanges and MetaTrader 5 over a single MCP endpoint, enabling trading and account management with server-side risk controls, paper trading by default, and auditable signed receipts.3CC BY-4.0- AlicenseNot gradedqualityBmaintenanceEquips AI agents with institutional risk management and execution tools for Solana and Hyperliquid, enabling Kelly-criterion position sizing, VaR/CVaR analysis, Monte Carlo simulations, circuit breaker checks, and wallet/funding data queries through standardized MCP tools.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Hyperliquid perpetual futures exchange for market analysis, account management, and risk-managed trading.51MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: market data (get_book, get_candles), account state (get_limits, get_positions), order actions (place_order, cancel_order, close_position, set_stop_loss), and audit (get_recent_decisions). While place_order, set_stop_loss, and close_position all involve orders, their descriptions clarify the specific action and constraints, so an agent can easily select the right one.
All tool names use consistent snake_case with a verb_noun structure (get_, place_, set_, cancel_, close_). No deviations or mixed conventions, making the naming predictable.
The server provides 9 tools covering market data, account information, order management, risk limits, and an audit log. This is a well-scoped set for a trading agent—neither too thin nor too heavy—with each tool earning its place.
Core trading workflows are covered: checking limits, viewing positions, placing/canceling orders, setting stop-losses, closing positions, and reviewing recent decisions. However, there is no direct way to list currently open/resting orders or query a specific order's status, which are notable gaps for order management, though agents may partially work around this via the decisions log.