SODAX Builders MCP Server

Get all borrowers across all money market assets with pagination

Get detailed configuration for all spoke chains including contract addresses, RPCs, and token configs

Get full SODAX configuration including all supported chains, swap tokens, and protocol settings in one call

Get OHLCV candlestick chart data for an AMM pool

Get AMM liquidity provider NFT positions, optionally filtered by owner address

Get borrowers for a specific money market asset by its reserve address

Get suppliers (lenders) for a specific money market asset by its reserve address

Get SODA token circulating supply as a plain number

Get assets representing spoke tokens on the hub (Sonic) chain, optionally filtered by source chain

Look up a specific intent by its intent hash (different from transaction hash)

Get detailed information for a specific money market asset by its reserve address

List all assets available for lending and borrowing in the SODAX money market

Get money market reserve assets used as collateral backing

Get tokens supported for money market lending/borrowing, optionally filtered by chain

Get current orderbook entries showing pending/open intents

Get volume and activity summary for a specific integration partner by their receiver address

List all SODAX integration partners including wallets, DEXs, and other protocols

Get mapping between chain IDs and intent relay chain IDs used by the SODAX relay network

Get solver-side details for an intent including fill history. Use includeAll to see all solver documents.

Get the solver's oracle USD prices per (chain, token). For quoting with sodax_get_solver_quote, filter chainId='146': chainId-146 addresses pass the quote service's compatibility check, while spoke-chain (non-146) addresses are rejected with 'not compatible with the quote service'. Caveat: passing that check (being listed/priced) does NOT guarantee a swap route — canonical bridged *_ASSET hub tokens and major stablecoins route most reliably, while many wrapped/derivative/money-market entries (e.g. WBTC, waLocBTC, SONIC_SODA_ASSET) are priced but frequently return 'No path was found', and routability is pair/amount/liquidity-dependent. Also useful for sanity-checking quote amounts against the USD prices the solver uses.

Get a swap quote from the SODAX solver. tokenSrc/tokenDst MUST be hub-chain (Sonic, chainId 146) asset addresses — look them up with sodax_get_solver_oracle (chainId='146'). Working example: tokenSrc='0xeb0393893b5bf98a50073d6740738b08e575058b' (BTC_BTC_ASSET) → tokenDst='0xaeafa26e43f46cd83efe89b1e57c858eb5685a24' (ETH_ASSET), amount='99800', quoteType='exact_input' returns a quoted_amount. exact_input quotes the destination amount you'd receive; exact_output quotes the source amount you'd need. There are two distinct HTTP-400 failures, both naming the two addresses: (1) 'not compatible with the quote service' = an address isn't a recognized hub asset (a spoke-chain or otherwise non-chainId-146 address was passed) → use a chainId-146 address from sodax_get_solver_oracle, and for a reliable pick prefer a canonical bridged *_ASSET hub token or major stablecoin (chainId 146 alone doesn't guarantee a route). (2) 'No path was found between X and Y' = both tokens are valid hub assets but the solver couldn't route this pair for this amount → routing is pair/amount/liquidity-dependent, so retry with a smaller amount or a more liquid counterparty (a canonical bridged *_ASSET token, or a major stablecoin like SONIC_USDC_ASSET). Many wrapped/derivative entries (e.g. WBTC, waLocBTC, SONIC_SODA_ASSET) are oracle-priced but frequently have no route — prefer canonical bridged *_ASSET hub tokens.

List all blockchain networks supported by SODAX for cross-chain swaps and DeFi operations

Get available tokens for swapping on SODAX, optionally filtered by chain

Get SODA token supply information including total, circulating, and burned amounts

Get SODA token total supply as a plain number

Look up a specific transaction by its hash to see status, amounts, and details

Get a user's lending and borrowing position in the money market

Get intent/transaction history for a specific wallet address

Get solver volume data showing filled intents with filtering and pagination. Requires inputToken and outputToken. Optional filters: chain, solver, block range OR time range (don't mix both).

Get aggregate solver volume stats: the approximate total number of filled-intent records (fill documents, not distinct intents). Cached ~60s upstream.

Clear both the backend API cache and the solver oracle cache to force fresh fetches on next requests. Reports the number of entries cleared per cache.

Fetch a single relay packet by its connection serial number (conn_sn). Returns the packet data on success or a `{success:false, message}` shape if the packet isn't found.

List every cross-chain packet emitted by a given source transaction. Use this to track relay status — a packet is complete when status='executed' and dst_tx_hash is populated.

Submit a confirmed spoke-chain transaction to the SODAX intent relay so it can be delivered to the destination chain. The tx must already be finalized on the source chain. Re-submitting the same tx is a no-op. For split-tx chains (Solana, Bitcoin) supply the optional `data` argument.

[SDK Docs] Fetch the full markdown content of a specific documentation page from Docs. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g. https://docs.sodax.com//getting-started). Since `searchDocumentation` returns partial content, use `getPage` to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.

Check SDK documentation availability. Call this first if docs tools seem unavailable.

List all SDK documentation tools with parameters. Essential for discovering what's available.

Reconnect to SDK documentation and refresh available tools. Use if docs seem stale or unavailable.

[SDK Docs] Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

[SDK Docs] Report an issue in the documentation of Docs so the team can fix it. Use it whenever, while helping a user, you come across content that is outdated, contradictory, missing information, or otherwise unhelpful. Also use it when the user themselves reports a problem with the docs, even if you could not verify it yourself. If it's your own observation, do a quick sanity check that the issue is real before reporting — no need to exhaustively re-read the page. Send one call per distinct issue and do not report the same issue twice in a conversation. Do not use this tool to confirm that a page is accurate; it is for reporting problems only.