Server Details
Live cross-network DeFi API data and auto-updating SDK docs for 17+ networks.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- gosodax/builders-sodax-mcp-server
- GitHub Stars
- 7
- Server Listing
- SODAX Builders MCP
See and control every tool call
Available Tools
15 toolsdocs_healthInspect
Check SDK documentation availability. Call this first if docs tools seem unavailable.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
docs_list_toolsInspect
List all SDK documentation tools with parameters. Essential for discovering what's available.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
docs_refreshInspect
Reconnect to SDK documentation and refresh available tools. Use if docs seem stale or unavailable.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
docs_searchDocumentationInspect
[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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
sodax_get_money_market_assetsInspect
List all assets available for lending and borrowing in the SODAX money market
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
| chainId | No | Filter by chain ID |
sodax_get_orderbookInspect
Get current orderbook entries showing pending/open intents
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of orders to return (1-100) | |
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
sodax_get_partnersInspect
List all SODAX integration partners including wallets, DEXs, and other protocols
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
sodax_get_supported_chainsInspect
List all blockchain networks supported by SODAX for cross-chain swaps and DeFi operations
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
sodax_get_swap_tokensInspect
Get available tokens for swapping on SODAX, optionally filtered by chain
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
| chainId | No | Filter tokens by chain ID (e.g., 'base', 'ethereum', 'icon') |
sodax_get_token_supplyInspect
Get SODA token supply information including total, circulating, and burned amounts
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
sodax_get_transactionInspect
Look up a specific transaction by its hash to see status, amounts, and details
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
| txHash | Yes | The transaction hash to look up (e.g., '0x...') |
sodax_get_user_positionInspect
Get a user's lending and borrowing position in the money market
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
| chainId | No | Filter by chain ID | |
| userAddress | Yes | The wallet address to look up |
sodax_get_user_transactionsInspect
Get intent/transaction history for a specific wallet address
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of transactions to return (1-100) | |
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
| offset | No | Number of transactions to skip for pagination | |
| userAddress | Yes | The wallet address to look up (e.g., '0x...') |
sodax_get_volumeInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order by block number | desc |
| limit | No | Maximum number of filled intents to return (1-100) | |
| since | No | Start time ISO format (don't mix with fromBlock/toBlock) | |
| until | No | End time ISO format (don't mix with fromBlock/toBlock) | |
| cursor | No | Pagination cursor from previous response's nextCursor | |
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
| solver | No | Filter by solver address (0x0...0 for default solver) | |
| chainId | No | Filter by chain ID (e.g., 146 for Sonic) | |
| toBlock | No | End block number (don't mix with since/until) | |
| fromBlock | No | Start block number (don't mix with since/until) | |
| inputToken | Yes | REQUIRED: Input token address | |
| includeData | No | Include raw intent data in response | |
| outputToken | Yes | REQUIRED: Output token address |
sodax_refresh_cacheInspect
Clear the cached API data to force fresh fetches on next requests
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.