Account-free crypto swaps: assets, routes, limits, live quotes, address checks, swap status
Maintained by@sablebolt(verified)Also a maintainer?
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Creates the swap and returns the payment instruction: the one-time deposit address, the memo if the chain needs one, the exact amount in decimal and in base units with the decimals and token contract as listed by the liquidity partner, a wallet URI where a standard exists (BIP-21, ERC-681, Solana Pay, Monero, TON), and the status URL. Use it only when you control the wallet at fromAddress and will send the deposit yourself; for a person use swap_page_link. The deposit must come from fromAddress; there is no refund address — a swap that cannot be completed is handled by support from the swap id. Floating rate: the final amount is set when the deposit confirms.
asset slug to receive, e.g. btc
asset slug you send, e.g. usdt-trc20
decimal amount you send, as a string, within get_limits
the receiving address for the `to` asset
the address you will send the deposit from (a wallet you control)
memo / destination tag / payment ID for the receiving side, only where that asset needs one
the sending side's extra id, only if your wallet attaches one
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http swaps https://api.sablebolt.io/mcp
Creates the swap and returns the payment instruction: the one-time deposit address, the memo if the chain needs one, the exact amount in decimal and in base units with the decimals and token contract as listed by the liquidity partner, a wallet URI where a standard exists (BIP-21, ERC-681, Solana Pay, Monero, TON), and the status URL. Use it only when you control the wallet at fromAddress and will send the deposit yourself; for a person use swap_page_link. The deposit must come from fromAddress; there is no refund address — a swap that cannot be completed is handled by support from the swap id. Floating rate: the final amount is set when the deposit confirms.
| Argument | Type | Description |
|---|---|---|
| to* | string | asset slug to receive, e.g. btc |
| from* | string | asset slug you send, e.g. usdt-trc20 |
| amount* | string | decimal amount you send, as a string, within get_limits |
| extraId | string | memo / destination tag / payment ID for the receiving side, only where that asset needs one |
| toAddress* | string | the receiving address for the `to` asset |
| fromAddress* | string | the address you will send the deposit from (a wallet you control) |
| fromExtraId | string | the sending side's extra id, only if your wallet attaches one |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"from",
"to",
"amount",
"fromAddress",
"toAddress"
],
"properties": {
"to": {
"type": "string",
"description": "asset slug to receive, e.g. btc"
},
"from": {
"type": "string",
"description": "asset slug you send, e.g. usdt-trc20"
},
"amount": {
"type": "string",
"description": "decimal amount you send, as a string, within get_limits"
},
"extraId": {
"type": "string",
"description": "memo / destination tag / payment ID for the receiving side, only where that asset needs one"
},
"toAddress": {
"type": "string",
"description": "the receiving address for the `to` asset"
},
"fromAddress": {
"type": "string",
"description": "the address you will send the deposit from (a wallet you control)"
},
"fromExtraId": {
"type": "string",
"description": "the sending side's extra id, only if your wallet attaches one"
}
}
}Minimum and maximum amount for a route, in the asset you send.
| Argument | Type | Description |
|---|---|---|
| to* | string | asset slug you receive, e.g. btc |
| from* | string | asset slug you send, e.g. usdt-trc20 |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"description": "asset slug you receive, e.g. btc"
},
"from": {
"type": "string",
"description": "asset slug you send, e.g. usdt-trc20"
}
}
}Floating estimate for a route and amount: amountTo, networkFee (taken out of the payout), receiveAmount, rate. The final amount is set when the deposit confirms.
| Argument | Type | Description |
|---|---|---|
| to* | string | |
| from* | string | |
| amount* | string | decimal amount you send, as a string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"from",
"to",
"amount"
],
"properties": {
"to": {
"type": "string"
},
"from": {
"type": "string"
},
"amount": {
"type": "string",
"description": "decimal amount you send, as a string"
}
}
}Status of one swap by id: stage (1 waiting … 5 done), deposit and payout addresses, amounts, both transaction hashes.
| Argument | Type | Description |
|---|---|---|
| id* | string | swap id from the status page URL |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "swap id from the status page URL"
}
}
}Every asset the swap form knows, with slug, ticker, network, confirmations, extra-id name and whether it is available right now.
No arguments.
{
"type": "object",
"properties": {}
}Every route with its own page (from/to slugs) and whether both sides are available right now.
No arguments.
{
"type": "object",
"properties": {}
}The page where the person completes the swap, with the amount prefilled. A swap for a person is completed by that person on the page: open the link, check the amount, both addresses and the memo on screen, then send the deposit from your own wallet. An agent that controls the sending wallet itself uses create_swap and pays the instruction it gets back.
| Argument | Type | Description |
|---|---|---|
| to* | string | |
| from* | string | |
| amount | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string"
},
"from": {
"type": "string"
},
"amount": {
"type": "string"
}
}
}Whether an address has the right format for an asset. Does not check who owns it or whether an exchange needs a memo.
| Argument | Type | Description |
|---|---|---|
| asset* | string | asset slug |
| address* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"asset",
"address"
],
"properties": {
"asset": {
"type": "string",
"description": "asset slug"
},
"address": {
"type": "string"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 3, 2026.