Home / MCP registry index / io.github.profitphil/qmax
io.github.profitphil/qmax
io.github.profitphil/qmax in the official MCP registry.
Endpoint https://qmax.exchange/api/mcp. Source: github.com/profitphil/qmax.
The registry describes it as: Qubic DEX aggregator: best-price quotes across QX and QSwap, order books, candles, trade plans.
We read its 19 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
qmax_list_assets qmax_get_quote qmax_build_plan qmax_get_health qmax_get_tape qmax_get_flow qmax_get_sellers qmax_swap_quote qmax_get_wallet_ledger qmax_get_liquidity_positions qmax_get_liquidity_pool qmax_get_candles qmax_get_price_history qmax_get_order_book qmax_check_arbitrage qmax_venue_premium qmax_list_pools qmax_pool_detail qmax_backtest
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-profitphil-qmax)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.