CCXT vs Hyperevm MCP
A side-by-side look at the CCXT and Hyperevm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CCXT for finance & fintech work; choose Hyperevm MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose CCXT when
- You need dedicated capabilities in the Finance & Fintech domain.
- You want tools like
list_exchanges, describe_exchange, describe_method.
Choose Hyperevm MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You want tools like
hyperevm_yields, hyperevm_protocols, hl_market.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 64/100 · Good | 59/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 44,480 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 32 | 9 |
| Full listing | View CCXT | View Hyperevm MCP |
Tools & capabilities
CCXT tools 32
list_exchangesList every exchange this server supports (built from ccxt.exchanges at runtime), with name, websocket and prediction-market availability. Filter by a name query or by support for a unified method.describe_exchangeOne exchange's supported unified methods, market types, timeframes, required credential fields, sandbox availability and documentation URLs. Per-method detail lives in describe_method.describe_methodSearch unified method names by keyword, or get one method's signature and parameter documentation. With "exchange" it adds that exchange's own docs (including supported params.* keys and links to the exchange API reference), per-market-type feature support, and searches its implicit (exchange-specific) endpoints too. Full ccxt manual: https://docs.ccxt.com/search_marketsSearch and filter the markets of one exchange (by text, base, quote, settle currency, market type), paginated. Use this to resolve unified symbols — there is deliberately no list-all-markets tool. On prediction exchanges use search_events instead.get_tickers24h price tickers for one or more unified symbols on an exchange (outcome handles on prediction exchanges).get_orderbookCurrent order book (bids and asks) for one unified symbol.get_ohlcvHistorical OHLCV candlestick data for a symbol and timeframe. Rows are [timestampMs, open, high, low, close, volume]. Page back with "since"; "params.until" bounds the end.get_tradesRecent public trades for one unified symbol.search_eventsSearch events on a prediction-market exchange (polymarket, kalshi, limitless, myriad, hyperliquid with prediction=true). A scoping filter is required: query, tags, or params.eventId/params.slug. Returns events with their markets and outcome handles — outcome handles are what you pass as the symbol to get_tickers/get_orderbook/create_order on prediction exchanges.call_read_methodEscape hatch covering every unified read method not served by a dedicated tool (fetchFundingRate, fetchLedger, fetchOpenInterest, fetchLiquidations, fetchEvent, fetchSettlements, …). Only fetch*/load* methods are accepted — writes are structurally rejected. Get the signature first with describe_method. Docs: https://docs.ccxt.com/call_implicit_getCall an exchange-specific implicit REST endpoint over HTTP GET, for data the unified API does not cover. Pass the implicit method name in the "method" argument (e.g. "publicGetTickerPrice"); these are exchange-specific — find them with describe_method {"query": ..., "exchange": ...} (its results list the name to pass here). The response is the raw exchange payload. Consult the exchange API reference (describe_exchange .urls.doc) and the ccxt manual: https://docs.ccxt.com/get_safety_statusWhat this server is currently allowed to do: configured accounts (names only — never credentials), enabled capability tiers, caps, sandbox/live environments, journal location, unresolved order intents, and any configuration problems.- +20 more on the listing page
Hyperevm MCP tools 9
hyperevm_yieldsEvery way to earn on Hyperliquid / HyperEVM, ranked in one table: liquid staking tokens (kHYPE, stHYPE, beHYPE), lending markets with supply and borrow rates, utilisation and max LTV, and LP or looping pools. Separates yield a pool earns from yield paid in emitted tokens, and anchors everything against what the network itself pays for staking. Start here for "where is the best yield"; use hyperevm_pool_history to see whether one of these rates has held. Read-only, public data, no API key.hyperevm_protocolsWhat is deployed on Hyperliquid / HyperEVM and how big it is: every protocol's TVL on this chain, its category, and how that TVL moved over 1 and 7 days, plus the chain total. Sort by size or by weekly growth. Pass a name for a detail card with audit links, site and socials. Read-only, public data, no API key.hl_marketPrices and market state on Hyperliquid right now: perp mark and oracle price, 24h move, funding (hourly and annualised), open interest, volume and max leverage, plus spot pair prices. Pass a symbol for one market with predicted funding on Hyperliquid, Binance and Bybit side by side. This is the current snapshot; for how funding behaved over past days use hl_funding. Read-only, public data, no API key.hl_stakingStaking HYPE directly with a validator: the active set ranked by predicted APR, with each one's commission, uptime and share of stake, and jailed validators named but excluded. This is what the network pays before any liquid staking wrapper takes its cut, so it is the benchmark every kHYPE or stHYPE rate should be judged against — those live in hyperevm_yields. Read-only, public data, no API key.hyperevm_walletLook up what any public Hyperliquid address holds: account value, margin, open perp positions with entry price, unrealised PnL and liquidation price, spot balances, and delegated HYPE. Works on any address, including one that is not yours — this reads the public ledger, and the server has no key, no signature and no send path with which to act on an address.hyperevm_pool_historyHow one pool's APY and TVL moved over the past weeks, separating yield the pool earned from yield paid out in emitted tokens. Answers whether a headline rate is stable, decaying, or propped up by rewards that can stop, and lets a number from hyperevm_yields be checked against its own history. Pass a pool by symbol, e.g. kHYPE or WHYPE-USDC. Read-only, public data, no API key.hyperevm_feesFees actually paid to protocols on Hyperliquid, over 24h, 7d and 30d, ranked. TVL shows how much money sits somewhere; fees show whether anyone is paying to use it, so the two rankings often disagree. Pass a name for one protocol's fee line. Read-only, public data, no API key.hl_fundingFunding rate history for one Hyperliquid perp — how the rate actually behaved over the past days, not just its value right now: average, range, how much of the time it stayed positive, and what holding the position would have paid. Includes the current predicted rate on Binance and Bybit for comparison. Use this when the question is whether a funding spread is durable rather than what it is this hour. Read-only, public data, no API key.hl_orderbookResting order book depth for one Hyperliquid market: spread, top of book, and how much size sits on each side. Pass size_usd to walk the book for that trade and get the average fill price and slippage — or a clear statement that the visible book is not deep enough to answer, which is common for large sizes. Answers "can I actually get in or out at this size", which price and volume alone do not. Read-only, public data, no API key.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
CCXT
No confirmed install command for CCXT yet — follow the setup steps linked from its listing page rather than a guessed package name.
Hyperevm MCP
{
"mcpServers": {
"sand0vvv-hyperevm-mcp": {
"command": "npx",
"args": [
"-y",
"@sand0vvv/hyperevm-mcp"
]
}
}
}
Frequently asked questions
CCXT is categorized under Finance & Fintech and uses an install path we have not confirmed yet. Hyperevm MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick CCXT for finance & fintech work and Hyperevm MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. CCXT has no confirmed install command yet — follow its own setup instructions.
CCXT has no declared pricing — check the project's own site. Hyperevm MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ccxt and sand0vvv-hyperevm-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CCXT has a quality signal of 64/100 (Good) with 2 views, 0 installs and 44,480 GitHub stars. Hyperevm MCP has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.