Sato Hub
MCP

SODAX Builders MCP

MCP server giving AI coding agents live access to SODAX's cross-network DeFi API across 20+ chains.

  • Sato Score83
  • ChainsEthereum, Base +3
ActiveUnverifiedActive · 2d ago

SODAX Builders MCP is an open-source MCP server on Ethereum, Base, Arbitrum and other chains, with last code activity on 2026-10-19 (Active). Latest release on 2026-08-03. Sato Score 83/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install SODAX Builders MCP →

Last commit Oct 19, 2026 · Last release Aug 3, 2026 (builders-sodax-mcp-server-v1.6.0) · ★ 9

Listed from builders.sodax.com on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-25. Evidence →

Next step

Watch SODAX Builders MCP

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on gosodax/builders-sodax-mcp-server before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

SODAX Builders MCP connects AI coding assistants to SODAX's cross-chain DeFi execution API, exposing 34+ tools (six categories: network config, intents/solver, intent relay, AMM/liquidity, money market, partners/token) for token swaps, money-market lending rates, solver volume, AMM liquidity/OHLCV data, and intent history across 20+ networks. An agent builder uses it to query live DeFi data and pull auto-synced SDK documentation directly inside a coding agent, without leaving the MCP session.

Sato Score

83/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
17/20
Interface verifiability
10/10
Docs & demo
6/10
Listing transparency & provenance
13/15
Independent verification
2/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Evidence — listed vs checked · what the words mean

Listed from builders.sodax.com on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-25.

ClaimValueEvidenceSourceChecked
Chains supportedEthereum, Base, Arbitrum, Optimism, Polygonself-reporteddocs.sodax.comas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedbuilders.sodax.comas of 2026-10-21
Recent activitylast release 2026-08-03 · last commit 2026-10-19observedgithub.com/gosodax/builders-sodax-mcp-server2026-10-21
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/gosodax/builders-sodax-mcp-server2026-09-25
MCP endpoint answersanswered — 37 tools listedobservedbuilders.sodax.com2026-10-21
Daily check record88 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Deploys ashosted remote MCP server (streamable HTTP), SSE (legacy), Docker, self-hostedconfidence 0.80self-reportedgithub.com/gosodax/builders-sodax-mcp-serveras of 2026-10-06
Works withClaude, Cursor, VS Code, Windsurf, ChatGPT, Gemini CLIconfidence 0.85self-reportedgithub.com/gosodax/builders-sodax-mcp-serveras of 2026-10-06
Tagsmcp, defi, cross-chain, swaps, sdk-docs, money-market, lending, solver, intents…confidence 0.80self-reportedgithub.com/gosodax/builders-sodax-mcp-serveras of 2026-10-06
Sato Score83/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Sep 25, 2026

Runtime: Node.js >=22.9.0 (TypeScript, pnpm) — hosted remote endpoint also available

git clone https://github.com/gosodax/builders-sodax-mcp-server
cd builders-sodax-mcp-server
pnpm install
pnpm build
pnpm start   # = node --env-file-if-exists=.env dist/index.js; or connect to the hosted server: {"mcpServers": {"sodax-builders": {"url": "https://builders.sodax.com/mcp"}}}

You supply: PORT — optional, default 3000, TRANSPORT — optional, default http, NODE_ENV — set to production for deployment, LOG_LEVEL — optional, default info, DISCORD_WEBHOOK_URL — optional, for Discord alerts, .env.example provided as a template

MCP invocation: node dist/index.js (http, local — what `pnpm start` runs); hosted: https://builders.sodax.com/mcp (Streamable HTTP), legacy SSE at https://builders.sodax.com/sse

Read from the project’s own docs as of 2026-09-25. What a deploy spec is →

Tool inventory — 37 tools, probed live 2026-10-21

  • sodax_get_supported_chains — List all blockchain networks supported by SODAX for cross-chain swaps and DeFi operations
  • sodax_get_swap_tokens — Get available tokens for swapping on SODAX, optionally filtered by chain
  • sodax_get_transaction — Look up a specific transaction by its hash to see status, amounts, and details
  • sodax_get_user_transactions — Get intent/transaction history for a specific wallet address
  • sodax_get_volume — 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).
  • sodax_get_volume_stats — Get aggregate solver volume stats: the approximate total number of filled-intent records (fill documents, not distinct intents). Cached ~60s upstream.
  • sodax_get_orderbook — Get current orderbook entries showing pending/open intents
  • sodax_get_money_market_assets — List all assets available for lending and borrowing in the SODAX money market
  • sodax_get_user_position — Get a user's lending and borrowing position in the money market
  • sodax_get_partners — List all SODAX integration partners including wallets, DEXs, and other protocols
  • sodax_get_token_supply — Get SODA token supply information including total, circulating, and burned amounts
  • sodax_get_all_config — Get full SODAX configuration including all supported chains, swap tokens, and protocol settings in one call
  • sodax_get_relay_chain_id_map — Get mapping between chain IDs and intent relay chain IDs used by the SODAX relay network
  • sodax_get_all_chains_configs — Get detailed configuration for all spoke chains including contract addresses, RPCs, and token configs
  • sodax_get_hub_assets — Get assets representing spoke tokens on the hub (Sonic) chain, optionally filtered by source chain
  • sodax_get_money_market_tokens — Get tokens supported for money market lending/borrowing, optionally filtered by chain
  • sodax_get_money_market_reserve_assets — Get money market reserve assets used as collateral backing
  • sodax_get_amm_positions — Get AMM liquidity provider NFT positions, optionally filtered by owner address
  • sodax_get_amm_pool_candles — Get OHLCV candlestick chart data for an AMM pool
  • sodax_get_intent — Look up a specific intent by its intent hash (different from transaction hash)
  • sodax_get_solver_intent — Get solver-side details for an intent including fill history. Use includeAll to see all solver documents.
  • sodax_get_money_market_asset — Get detailed information for a specific money market asset by its reserve address
  • sodax_get_asset_borrowers — Get borrowers for a specific money market asset by its reserve address
  • sodax_get_asset_suppliers — Get suppliers (lenders) for a specific money market asset by its reserve address
  • sodax_get_all_borrowers — Get all borrowers across all money market assets with pagination
  • sodax_get_partner_summary — Get volume and activity summary for a specific integration partner by their receiver address
  • sodax_get_total_supply — Get SODA token total supply as a plain number
  • sodax_get_circulating_supply — Get SODA token circulating supply as a plain number
  • sodax_refresh_cache — 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.
  • sodax_get_solver_oracle — 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-ch
  • sodax_get_solver_quote — 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=
  • sodax_relay_submit_tx — 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
  • sodax_relay_get_transaction_packets — 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.
  • sodax_relay_get_packet — 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.
  • docs_health — Check SDK documentation availability. Call this first if docs tools seem unavailable.
  • docs_refresh — Reconnect to SDK documentation and refresh available tools. Use if docs seem stale or unavailable.
  • docs_list_tools — List all SDK documentation tools with parameters. Essential for discovering what's available.
Answers a handshake
yes · 2026-10-21
Answers a call
not asked — no tool is named as a read (list_/get_/search_)

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-23

97.8%of 91 checks since 2026-07-23 succeeded
Currently responding for 17 days
Succeeded
89
Failed
2
Their error
0
Unattributed
2

State changed on 2026-09-17 (responding → unreachable from our probe), 2026-09-18 (unreachable from our probe → responding), 2026-10-04 (responding → unreachable from our probe), 2026-10-05 (unreachable from our probe → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
37
from the server's own tools/list · 29/30 days
Sato Score
83
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Tool inventory history — 37 now, peak 40, since 2026-07-23

  • 2026-09-04 40 → 37 −3 (docs_getPage, docs_searchDocumentation, docs_sendFeedback)

Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.

Details

Chains
Ethereum, Base, Arbitrum, Optimism, Polygon
Agent types
MCP server
Open source
Yes
Pricing
Free
Deploys as
hosted remote MCP server (streamable HTTP), SSE (legacy), Docker, self-hosted
Works with
Claude, Cursor, VS Code, Windsurf, ChatGPT, Gemini CLI
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#defi#cross-chain#swaps#sdk-docs#money-market#lending#solver#intents#amm

Where SODAX Builders MCP fits

Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from SODAX Builders MCP, pulled from its GitHub and X.

Listing History

Recorded changes to SODAX Builders MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 6, 2026
    Auto-enriched: deployment options, supported integrations, tags
  2. Sep 25, 2026
    Verified: deploy spec
  3. Sep 18, 2026
    Sato Score tier: Medium → High
    Score 69 → 78.
  4. Sep 17, 2026
    Sato Score tier: High → Medium
    Score 79 → 69.
  5. Aug 3, 2026
    New release published
  6. Jul 24, 2026
    Sato Hub began tracking this listing
  7. Jul 20, 2026
    Edited: mcp endpoint url
  8. Jul 19, 2026
    Edited: description long
  9. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about SODAX Builders MCP

Is SODAX Builders MCP open source?
Yes. SODAX Builders MCP is open source under the MIT license; the repository is https://github.com/gosodax/builders-sodax-mcp-server. Checked as of 2026-10-21.
Which chains does SODAX Builders MCP support?
SODAX Builders MCP lists support for Ethereum, Base, Arbitrum, Optimism, Polygon as of 2026-10-21.
Is SODAX Builders MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-10-19 (last commit 2026-10-19, last release 2026-08-03), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run SODAX Builders MCP?
Node.js >=22.9.0 (TypeScript, pnpm) — hosted remote endpoint also available. Install: git clone https://github.com/gosodax/builders-sodax-mcp-server && cd builders-sodax-mcp-server && pnpm install && pnpm build. Entry: pnpm start # = node --env-file-if-exists=.env dist/index.js; or connect to the hosted server: {"mcpServers": {"sodax-builders": {"url": "https://builders.sodax.com/mcp"}}}. Sato Hub reproduced this install in a container on 2026-09-25. It runs as an MCP server (node dist/index.js (http, local — what `pnpm start` runs); hosted: https://builders.sodax.com/mcp (Streamable HTTP), legacy SSE at https://builders.sodax.com/sse).
Is SODAX Builders MCP verified on Sato Hub?
Sato Hub holds one earned check for SODAX Builders MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 83 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "SODAX Builders MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/sodax-builders-mcp

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.