mcp-hylo
Related Servers
Alternatives to mcp-hylo
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to query Solana balances, SPL and Token-2022 holdings, transaction summaries, and recent activity, and to dry-run SOL transfers through read-only tools. It validates inputs and never signs or broadcasts transactions.5181 npmMIT
- AlicenseAqualityAmaintenanceProvides read-only access to the Hydromancer Hyperliquid API, letting AI apps query wallets, trades, top traders, markets, funding rates, order-book depth and liquidations in plain English. All requests go to the read-only /info endpoint, so it never places orders or handles funds or keys.12MIT
- AlicenseAqualityDmaintenanceProvides read-only access to Solana on-chain data, enabling natural language queries for wallet balances, token holdings, prices, transactions, and more via MCP-compatible clients.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query live Solana wallet token holdings, native SOL balances, transaction history, transaction details, and SPL token mint top holders through keyless public endpoints.254 npmMIT

magpie-mcpofficial
AlicenseNot gradedqualityAmaintenanceProvides LLMs and agents with read-only access to Magpie Capital's Solana lending protocol data, including live stats, collateral catalog, and per-token loan terms, plus guidance for agent borrowing via x402 endpoints.10 npm2MIT- AlicenseCqualityDmaintenanceA read-only Model Context Protocol server for Hyperliquid that exposes over 30 tools to query public market data and user state via the Hyperliquid Info API, without requiring a private key.41MIT
TDQS
Scored across 4 tools
Each tool targets a clearly distinct scope: protocol-wide state, Earn Pool state, per-wallet balances, and a conceptual explainer. The descriptions make the boundary between get_protocol_state and get_earn_pool_state explicit, so no realistic misselection.
All four tools follow a consistent snake_case verb_noun pattern: get_protocol_state, get_earn_pool_state, get_wallet_exposure, explain_mechanism. The single 'explain' verb is a reasonable deviation for a documentation tool and remains readable.
Four read-only tools is thin but each covers a genuinely distinct surface for a state-inspection server. Slightly minimal, but nothing feels redundant or wasted.
The read-only domain is well covered: protocol state, Earn Pool NAV, wallet exposure for the key assets (hyUSD, xSOL, eHYUSD), and an explainer. Minor gaps like historical/timeseries or per-asset detailed state exist, but core read paths are addressed.