Dexpaprika MCP vs Hyperevm MCP

A side-by-side look at the Dexpaprika MCP and Hyperevm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dexpaprika MCP logoDexpaprika MCPFinance & Fintech · Local subprocess (stdio)Coinpaprika's DexPaprika MCP server exposes high-performance DexPaprika API covering 20+ chains and 5M+ tokens with real time pricing, liquidity pool data & historical OHLCV data, providing AI agents standardized access to comprehensive market data through Model Context Protocol.68GreatAuth: no auth requiredHyperevm MCP logoHyperevm MCPFinance & Fintech · Local subprocess (stdio)Read-only Hyperliquid / HyperEVM: every way to earn on HYPE in one table — liquid staking, lending with utilisation and max LTV, LP pools, and the HLP vault — with yield a pool earns separated from yield paid in emitted tokens. Also protocol TVL, fees actually paid, perp and spot markets, funding history, and order-book depth with a straight answer when a size will not fill. Where a source publishes a figure whose unit cannot be confirmed, the cell reads n/a instead. No keys, no signing, nothing to configure. npx -y @sand0vvv/hyperevm-mcp59GoodAuth: not declared

Verdict: choose Dexpaprika MCP for finance & fintech work as a local process; 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?

Dexpaprika MCP logoChoose Dexpaprika MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: DEXPAPRIKA_API_KEY, DEXPAPRIKA_API_BASE_URL.
  • You want tools like getKeyStatus, getNetworks, getCapabilities.
Explore Dexpaprika MCP

Hyperevm MCP logoChoose 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.
Explore Hyperevm MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDexpaprika MCP logoDexpaprika MCPHyperevm MCP logoHyperevm MCP
CategoryFinance & FintechFinance & Fintech
Quality signal68/100 · Great59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsDEXPAPRIKA_API_KEYDEXPAPRIKA_API_BASE_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1080
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools179

Tools & capabilities

Dexpaprika MCP tools 17

  • getKeyStatusReport whether this server is sending an API key and which plan the API sees. Use when calls are being rate limited or refused, or when the user asks whether their DexPaprika key is working. Takes no arguments and reads no market data.
  • getNetworksList every blockchain network DexPaprika indexes, each row carrying its network id (slug), 24h volume, transaction count, and pool count. Read-only and keyless. Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires as its 'network' argument. Use for 'which chains do you support?', 'is Base/Solana/Arbitrum covered?', or 'what is the slug for Polygon?'. Returns the full array with no pagination or sorting; takes no parameters beyond a short rationale. For platform-wide totals rather than a per-network list use getStats.
  • getCapabilitiesGet the static agent onboarding guide for this server: supported workflows, network name synonyms (mapping words like 'eth' to the canonical slug 'ethereum'), recommended call sequences, and common pitfalls. Read-only and keyless. Read it once at the start of a session before your first query, or when asked 'how do I use this API?', 'what order should I call things in?', or 'which slug maps to eth?'. This returns onboarding docs, not live market data; for the actual list of network slugs use getNetworks, and for coverage totals use getStats. Takes no parameters beyond a short rationale.
  • getNetworkDexesList the DEXes (exchanges) operating on one network, such as Uniswap on ethereum or Raydium on solana, returned under 'dexes' with page_info (page, total_pages). Read-only and keyless. Use for 'which DEXes are on Base?', 'does Solana have Orca?', or to get a dex id to feed into getDexPools. Scope is a single network; call getNetworks first for the slug. Params: network (required slug); limit (default 10, max 100); page (default 1, 1-indexed); sort_by (only 'pool'; legacy alias order_by); sort_dir 'asc' or 'desc' (default 'desc'; legacy alias sort).
  • getNetworkPoolsGet the top liquidity pools across a whole network, ranked by 24h volume by default, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. This is the primary chain-wide pool discovery tool. Use for 'biggest pools on ethereum', 'top trading pairs on Base', or 'most active pools on Solana'. Narrow to one exchange with getDexPools, or apply numeric/time filters with getNetworkPoolsFilter. Params: network (required slug); limit (default 10, max 100); cursor (pass previous next_cursor to page); sort_by (default 'volume_usd_24h', canonical *_24h fields, alias order_by); sort_dir 'asc' or 'desc' (default 'desc', alias sort).
  • getDexPoolsGet the pools belonging to one specific DEX on one network, e.g. all Uniswap v3 pools on ethereum. Proxies /networks/{network}/pools/search with a dex_name filter (the old /networks/{network}/dexes/{dex}/pools endpoint was removed): rows come back under 'results' with cursor pagination (has_next_page + next_cursor), and the 24h volume field is volume_usd_24h. Read-only and keyless. Narrower than getNetworkPools (a single exchange, not the whole chain). Use for 'show me Raydium pools', 'top pairs on PancakeSwap', or 'liquidity on Orca'. Get the dex id from getNetworkDexes or search first, and pass that response's dex_id field ('uniswap_v3'), matched case-insensitively. Do not pass its dex_name field ('Uniswap V3'): a human display name returns HTTP 200 with an empty results[] rather than an error, so an empty answer here usually means the wrong form of the name was sent. Params: network (required slug); dex (required id, e.g. 'uniswap_v3'; the REST API calls this query parameter dex_name); limit (default 10, max 100); cursor (pass previous next_cursor to page); sort_by (default 'volume_usd_24h', canonical *_24h fields, short legacy names still accepted, alias order_by); sort_dir 'asc'/'desc' (default 'desc', alias sort). The old page number is gone: page 2 and above return an error pointing at cursor.
  • getNetworkPoolsFilterGet pools on one network filtered by numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getNetworkPools when the user gives numeric constraints or a time window. Use for 'pools over $1M liquidity on Base', 'pools created in the last 24h', or 'high-volume low-liquidity pairs'. Optional filters (AND-combined): volume_24h_min/max, volume_7d_min/max, liquidity_usd_min/max, txns_24h_min, created_after/created_before (Unix timestamps). Also network (required); limit (default 50, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort).
  • getPoolDetailsGet the full current snapshot for one pool by address: its two tokens, current price, liquidity/TVL, 24h volume, and transaction counts, returned as a single pool object (not a list). Read-only and keyless. Use after search or getNetworkPools surfaces a pool, or for 'price/TVL of this pool?' or 'details for pool 0x...'. Returns live values only; for historical candles use getPoolOHLCV, and for the raw swap feed use getPoolTransactions. Params: network (required slug); pool_address (required, e.g. '0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640'); inversed (optional bool, default false, flips the token price ratio to token1/token0).
  • getPoolOHLCVGet historical OHLCV candles (open, high, low, close, volume) for one pool over a time range, returned as a time-series array. Read-only and keyless. Use for 'price history of this pair', 'hourly chart for the last week', 'candles since Jan 1', or backtesting; for the single current price use getPoolDetails instead. Params: network (required); pool_address (required); start (required; Unix timestamp, RFC3339, or yyyy-mm-dd); end (optional, capped to 1 year after start); interval one of '1m','5m','10m','15m','30m','1h','6h','12h','24h' (default '24h'); limit (default 100, max 366 candles); inversed (optional bool, default false).
  • getPoolTransactionsGet one pool's recent individual swap transactions, newest first, returned under 'transactions' (paginate with page, or a cursor). Read-only and keyless. These are per-trade records, not aggregated candles (use getPoolOHLCV) or a summary snapshot (use getPoolDetails). Use for 'recent trades on this pool', 'who swapped in the last hour', or 'raw transaction feed'. Params: network (required); pool_address (required); limit (default 10, max 100); page (default 1, up to 100 pages) or cursor (a transaction id); from (optional Unix seconds, inclusive, capped to the last 7 days); to (optional Unix seconds, exclusive, must be after from).
  • getTokenDetailsGet one token's data and metadata by contract address on one network: multi-timeframe price and volume metrics, plus name, website, Twitter, and Telegram links, returned as a single token object. Read-only and keyless. Use for 'price and volume for 0x... on Base' or 'tell me about this token'. If you only have a symbol like WETH, call search first to resolve the address and network. For many tokens' prices at once use getTokenMultiPrices; for the pools holding this token use getTokenPools. Params: network (required slug); token_address (required contract address, e.g. 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' on solana).
  • getTokenPoolsGet the liquidity pools that contain a specific token on one network, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Use for 'which pools hold WETH on ethereum?' or 'liquidity venues for 0x...'. Network-scoped, so run search first if unsure of the network; unknown addresses return empty results, not an error. For the token's own price use getTokenDetails. Params: network (required); token_address (required); limit (default 10, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort). Extra params such as inversed or paired_token_address are unsupported and error.
  • +5 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.

Dexpaprika MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "coinpaprika-dexpaprika-mcp": {
      "command": "npx",
      "args": [
        "dexpaprika-mcp@latest"
      ],
      "env": {
        "DEXPAPRIKA_API_KEY": "YOUR_DEXPAPRIKA_API_KEY_HERE",
        "DEXPAPRIKA_API_BASE_URL": "YOUR_DEXPAPRIKA_API_BASE_URL_HERE"
      }
    }
  }
}

Hyperevm MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sand0vvv-hyperevm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sand0vvv/hyperevm-mcp"
      ]
    }
  }
}

Frequently asked questions

Dexpaprika MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Hyperevm MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Dexpaprika MCP 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.

Dexpaprika MCP is listed as free. Auth: no auth required. 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 coinpaprika-dexpaprika-mcp and sand0vvv-hyperevm-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dexpaprika MCP has a quality signal of 68/100 (Great) with 2 views, 0 installs and 108 GitHub stars. Hyperevm MCP has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.