Model Context Protocol (MCP) server for freee API integration
Qmax is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Qubic DEX aggregator: best-price quotes across QX and QSwap, order books, candles, trade plans.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http qmax-mcp https://qmax.exchange/api/mcp
# 2 — ask your agent for something these tools do
# qmax_list_assets, qmax_get_quote, qmax_build_plan and 16 more
Qmax costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http qmax-mcp https://qmax.exchange/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Lists assets that trade on QX and/or QSwap, most liquid first, or searches by symbol. Use this first to find the right asset symbol and to see 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Part of a symbol to search for, e.g. 'QD' |
| category | string | no | Only smart-contract shares or only tokens |
| limit | integer | no | Most assets to return |
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 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; qua
| Parameter | Type | Required | Notes |
|---|---|---|---|
| side | string | yes | — |
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| qty | integer | yes | How many units of the asset |
| slippage_bps | integer | no | Slippage tolerance in basis points (100 = 1%), applied to the limits in route[].execution |
| split | boolean | no | false prices the best single market only |
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 b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| side | string | yes | — |
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| qty | integer | yes | — |
| slippage_bps | integer | no | — |
| holdings_qx | integer | no | Selling only: units of this asset the wallet holds that QX manages |
| holdings_qswap | integer | no | Selling only: units of this asset the wallet holds that QSwap manages |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | no | Leave out for all assets (grade, score, flags, top reason each) |
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': pass it back as 'since' to get only newer trades. Served from
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | no | Only this asset (leave out for all) |
| limit | integer | no | — |
| since | integer | no | Only trades newer than this id (the latestId from an earlier call) |
| venue | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | no | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| window | string | no | — |
| venue | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
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 you should get) and 'minOutQty' (guaranteed by the limits only if neither price mo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Token to sell |
| to | string | yes | Token to buy |
| qty | integer | yes | How many units of 'from' to sell |
| slippage_bps | integer | no | — |
| compare | boolean | no | Also plan the same swap forced onto each single market (QX or QSwap per leg) and say what QMax's route is worth against them (bestDeal). Slower. |
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. Read 'warnings' and 'truncated': the archive has no events for about 10 to 14 June 2026, units that arrived before the wind
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identity | string | yes | The wallet's 60-letter identity |
| days | integer | no | — |
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 s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identity | string | yes | The wallet's 60-letter identity |
A QSwap pool's reserves (QU and tokens), total liquidity units and price, read from the contract. Use it to see how deep a pool is before talking about providing liquidity. Adding or removing liquidity each cost a flat 100,000 QU on top of any deposit. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
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: { ass
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| range | string | no | How far back to look. 'all' is everything QMax has (about six months). |
| interval | string | no | Candle width: a minute up to a day (default suits the range). One answer holds at most the latest 5,000 candles |
| venue | string | no | Which market's prices: QX (order book), QSwap (pool), 'all' (treat both as one market), or 'auto' (the market the live price comes from). |
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. Use qmax_get_candles for OHLC and volume.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| range | string | no | How far back to look. 'all' is everything QMax has (about six months). |
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). Use it to judge depth before sizing an order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| levels | integer | no | Price levels per side of the QX book |
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. A found result may be billed to the caller's QMax key (50 QU).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| min_profit_qu | number | no | Only an opportunity with at least this profit (QU) |
| min_profit_pct | number | no | Only one with at least this profit as a percentage of the QU put in |
| max_cost_qu | number | no | Most QU to put in (a budget); the search returns the best loop that fits |
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, p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| range | string | no | — |
| reference_qu | number | no | Trade size in QU used to work out the break-even gap (default 10,000,000) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window | string | no | — |
| sort | string | no | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| window | string | no | — |
| position_qu | number | no | — |
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 fract
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one. |
| range | string | no | — |
| venue | string | no | Which market's prices: QX (order book), QSwap (pool), 'all' (treat both as one market), or 'auto' (the market the live price comes from). |
| starting_qu | integer | yes | QU to start with, e.g. 10000000 |
| strategy | object | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Qmax or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| qmax_list_assets | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_quote | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_build_plan | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_health | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_tape | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_flow | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_sellers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_swap_quote | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_wallet_ledger | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_liquidity_positions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_liquidity_pool | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_candles | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_price_history | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_get_order_book | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_check_arbitrage | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_venue_premium | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_list_pools | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_pool_detail | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qmax_backtest | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Qmax can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.