mcpbeat Sign in

Qmax MCP Server

by profitphil Your server? Claim it
answering

Qmax is answering right now. Last checked 3 min ago. It exposes 19 tools. Last commit 18 Oct 2026.

Qubic DEX aggregator: best-price quotes across QX and QSwap, order books, candles, trade plans.

Uptime history 9 days of history
9 days agonow
100.0%
Uptime 24h
92 of 92 checks
19
Tools
read from the server
140 ms
Response time
average over 24h
0
Stars
last commit 18 Oct 2026

What changed 36

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 October 2026. No other catalogue keeps this.

24 Oct 10 tools changed the parameters they ask for qmax_backtest, qmax_build_plan, qmax_get_flow and 7 more
21 Oct 13 tool descriptions were rewritten14 times that day qmax_backtest, qmax_build_plan, qmax_check_arbitrage and 10 more
21 Oct 12 tools changed the parameters they ask for qmax_backtest, qmax_build_plan, qmax_check_arbitrage and 9 more
and 1 more, back to 21 October 2026

Nothing serious here today

Today is the operative word: we check Qmax every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add qmax --transport http https://qmax.exchange/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://qmax.exchange/api/mcp
~/.codex/config.toml
[mcp_servers.qmax]
url = "https://qmax.exchange/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "qmax": {
      "url": "https://qmax.exchange/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "qmax": {
      "type": "http",
      "url": "https://qmax.exchange/api/mcp"
    }
  }
}

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

qmax
qmax_backtest
Replays a strategy over real hourly trade data with the venues' real fees and reports what it would have done: final value, return, buy-and-hold comparison, max drawdown, fees paid, trades. Decisions are made on an hour's close and filled at the next hour's open; hours with no trades cannot be traded. Strategies: 'hold' (buy once, hold), 'dca' (spend amountQu every everyHours), 'bands' (buy fractionPct of the QU when the price is bandPct below its lookbackHours average, sell fractionPct of the holding when above, with a cooldown). The result's 'warnings' note that there is no order book depth in the history, so large amounts are optimistic, and QSwap's flat 100,100 QU fee can swallow small trades. Past results do not predict future ones.
qmax_build_plan
Quotes an order and returns the exact transactions a wallet must sign to carry it out, in order. QMax signs nothing and sends nothing: you (or the user) sign each step with your own wallet and broadcast it. Steps (in order): any share-management move needed first (selling shares that the other market manages), then one call per market. Each step: kind, description, destination (a smart contract by index), inputType (procedure number), amountQu to attach (QU that may leave the wallet; unused QU is refunded by the contracts) and payloadBase64 (the call's input bytes). 'maxOutlayQu' is the most QU that can leave the wallet across all steps, so it is the figure to compare with a spending limit before signing. Signing and sending a step moves real funds. For a sell, pass how many shares the wallet holds under QX management and under QSwap management (holdings_qx, holdings_qswap) so the right moves are planned. Buys need no holdings.
qmax_check_arbitrage
Searches, live and at full depth, for a profitable buy-on-one-market, sell-on-the-other loop after every venue fee, and returns the most profitable size or null. It is two separate transactions, so the second leg can fill worse than shown; this is a snapshot, not a guarantee. Only assets on both markets can have one. Free on qmax.exchange; a QMax server run with metered billing can charge a small fee for a found result.
qmax_get_candles
Open, high, low, close, QU volume, units and trade count per candle, built from every trade QX and QSwap logged (a minute wide at the finest; about six months back, which is all the Qubic archive has: its trade records begin in April 2026). A candle exists only where something traded, so a gap means no trades. The response also gives the last 24 hours of volume across both markets. Returns: { asset, range, interval, venue, candles: [{ t (ms), o, h, l, c, volumeQu, volumeQty, trades }], truncated?, available?, volume24hQu, trades24h }. Prices are QU per unit.
qmax_get_flow
Buy and sell volume (QU and units), trade counts and net pressure (positive = more buying) over the last hour or 24 hours, for one asset or the whole market. Direction is the taker's side. 'partial' is true while the server is still loading the window.
qmax_get_health
A 0 to 100 score and A to E grade for an asset, from its QX order book, its QSwap pool and six months of trades, with flags and plain-English reasons (most important first). Flags include thin-book, wide-spread, quiet, few-trades, new-listing, volume-spike, one-sided, pool-dominated and wash-suspected / bot-burst (a single wallet churning tiny same-size swaps against itself, which inflates trade counts but not volume). Many assets grade D or E because QX markets are thin: that is information, not an error. It is an automated estimate from public data and NOT advice; the absence of 'wash-suspected' is not proof of a clean market (large wash trades are not detectable from this data). Omit 'asset' to get every asset's grade in one call.
qmax_get_liquidity_pool
A QSwap pool's reserves (QU and tokens), total liquidity units and price, read from the contract. It shows how deep a pool is. Adding or removing liquidity each cost a flat 100,000 QU on top of any deposit. Read-only.
qmax_get_liquidity_positions
Every QSwap pool a wallet has liquidity in (public chain data, so any 60-letter identity works): its liquidity units, share of the pool, what removing it all would pay (QU and tokens, before QSwap's flat 100,000 QU fee) and its value in QU at the pool's own price, read live from the contract. Read-only. Adding or removing liquidity is done in the QMax app with a wallet; this tool never builds or signs one. 'complete' is false when a pool could not be read and its positions are missing. 'earnedFeesQu' is already inside what removing pays, nothing pays it separately. Values are estimates at the pool's price, which can be far from what the tokens sell for on a thin market.
qmax_get_order_book
What is resting on the QX order book (grouped by price, with cumulative size and cost from the best price outward, best bid/ask, spread) and the QSwap pool (reserves, price, and how far trades of 0.1% to 5% of the pool would move the price). It shows the depth available at each price.
qmax_get_price_history
The asset's price over time as points (ms timestamp, price in QU, and for recently recorded points the best bid, ask and pool price). Points before 'recordedSince' were rebuilt from past trades as hourly volume-weighted averages (marked src 'trades'); after it QMax recorded the price about every 10 minutes. OHLC and volume are in qmax_get_candles.
qmax_get_quote
Prices an order and finds the cheapest route across the QX order book and the QSwap pool, splitting the order across both when that is cheaper. Nothing is placed. Returns an openInQMax link (when the order can be filled) that opens QMax with this order filled in, for the person to review and sign in their own wallet. Also returns the total in QU, the average price, each leg (venue, quantity, price range, fees, price impact), what each single market alone would cost, a plain-English line saying what the routing saved, and warnings. All amounts are QU; quantities are whole units. The quote is a snapshot: prices move, so it can differ a moment later.
qmax_get_sellers
For the last 7 days: the wallets that sold the asset on QX or QSwap, how long each had held the units (each unit sold is matched, first in first out, to the purchase it came from), what they paid and whether they sold above or below that, with a plain-language reading ("what the numbers say"). Read from the public Qubic archive, so the first call for an asset starts the reading and answers status "working" with its progress and what is known so far; a reading takes a minute or two, after which the status is "ready" and the answer is kept for six hours. The chain shows who sold and what they paid, not why. Free.
qmax_get_tape
The most recent trades on both markets in one feed, newest first: time, market, asset, quantity, QU, price and direction. The direction is the TAKER's side (the person who started the trade): 'buy' or 'sell'. Rows also carry the transaction hash. The answer includes 'flow24h', the last 24 hours of buy versus sell volume, and 'latestId', the id to give as 'since' to get only newer trades. Served from memory, so cheap to poll.
qmax_get_wallet_ledger
Every QX and QSwap buy and sell a wallet made (read from public on-chain transfers, so any 60-letter identity works): price, QU net of fees, estimated fees, running position, and average-cost realized profit, plus current positions with unrealized profit and loss. ESTIMATED. The 'warnings' and 'truncated' fields say that the archive has no events for about 10 to 14 June 2026, units that arrived before the window or by transfer have no known cost (selling them is not counted as profit), and QSwap liquidity changes appear as transfers. Unrealized P&L uses the mid or pool price, which can mislead on thin markets. Takes a few seconds and many archive reads, so it is rate limited per address. Not tax advice.
qmax_list_assets
Lists assets that trade on QX and/or QSwap, most liquid first, or searches by symbol. Gives each asset's symbol and which markets it trades on ('QX', 'QSwap' or both: only assets on both can be split for a better price). Returns: { count, assets: [{ id, symbol, category ('contract' shares or 'token'), venues, priceQu, liquidityQu, activity }] }. Prices are QU per unit.
qmax_list_pools
Every QSwap liquidity pool with its TVL, trailing swap volume, estimated fee APR (from real swap volume; only 0.192% of each swap's volume reaches liquidity providers), price change and impermanent loss over the window. A trailing estimate: past fees do not predict future fees, and volume that looks inflated (wash trading) is flagged in each pool's notes.
qmax_pool_detail
One pool's numbers explained, and for a deposit size (position_qu, the QU value of both sides together) an estimate of fees per day, per 30 days and the impermanent loss for price moves of 10%, 25% and 50%. Adding and removing liquidity each cost a flat 100,000 QU.
qmax_swap_quote
Plans swapping one token for another as two linked trades: sell 'from' for QU (leg 1), then buy 'to' with the QU (leg 2), each routed across QX and QSwap by the best route. Read-only: nothing is signed. Returns both quotes, 'upfrontQu' (QU the wallet must hold before leg 1 for its flat fees), 'expectedOutQty' (what the swap should return) and 'minOutQty' (guaranteed by the limits only if neither price moves past the slippage limit), plus warnings. Leg 2 can only be sized exactly after leg 1 settles, from the wallet's real balance, so a swap is never one atomic transaction: if leg 1 completes and leg 2 cannot proceed you are left holding QU. Both tokens must trade on QX or QSwap; QU itself is not a swap leg (qmax_get_quote prices a plain purchase or sale for QU).
qmax_venue_premium
Hour by hour, the gap between the asset's QX and QSwap prices (positive = QSwap dearer) and how often it was wider than the trading costs for a trade of 'reference_qu'. This is an UPPER BOUND on arbitrage, not a profit: it uses hourly average prices, so it leaves out the QX bid-ask spread (often wider than the costs) and the delay between the two transactions. Returns { bothVenues, breakEvenPct, points, summary, note }.

Endpoints

URLTransportStateLatencyChecked
https://qmax.exchange/api/mcp streamable-http answering 137 ms 3 min ago

Alternatives to Qmax

same job, measured the same way
LCX Liberty DEX
by lcx-ag

Best-route swap quotes, token search and USD prices across EVM chains. Read-only, never trades.

5 tools answering
Onlyswaps
by nicofains1

DEX meta-aggregator for AI agents. Best prices from 15+ aggregators across 13 chains.

35 installs/wk local only
Akka Finance
by akka-finance

MCP server for AKKA Finance DEX aggregator — swap quotes, routes, and execution

28 installs/wk local only
LayerHop
by layerhop

Best-price cross-chain swap quotes across 70 chains (EVM + Solana). Holds no keys, never signs.

593 installs/wk 15 tools answering
FxSocket
by fxsocket

Read-only MetaTrader 4 and 5 accounts: balances, positions, trade history, quotes and candles.

answering
Iran Crypto Exchanges
by sepehr071

Unofficial read-only Iranian crypto exchanges: prices in Toman, order books, trades, candles.

1 298 installs/wk local only
Buda MCP
by gtorreal

Buda.com market data: prices, spreads, OHLCV, order books, trades, and volume for CLP, COP, PEN.

15 installs/wk local only
Industrial Platform Market Data
by industrial-platform-ai

Recurring crypto price, candles, order-book and market snapshot data for agents.

4 tools answering

Qmax — questions

Answers built from our own checks of this server.

What can Qmax do?
It exposes 19 tools, read directly from the server on our last check. Among them: qmax_backtest, qmax_build_plan, qmax_check_arbitrage, qmax_get_candles, qmax_get_flow, qmax_get_health and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Qmax working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 140 ms. The bar chart above shows every period we have measured.
How do I connect Qmax?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Qmax need an API key?
No. Qmax completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Qmax?
It answers our handshake in 140 ms on average, which is faster than 91% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Qmax open source?
We cannot say either way: written in TypeScript, 0 stars on GitHub and 1 open issue, but we could not determine the licence, and without one the code is not open source by default.