Sablebolt swaps
REMOTE · API.SABLEBOLT.IO
Account-free crypto swaps: assets, routes, limits, live quotes, address checks, swap status
Available components
Last scanned (20 hours ago)
Scores higher than 53% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.sablebolt.io/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sablebolt.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| sablebolt.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sablebolt.io/mcp | Unreachable | ||
| http (plaintext) | http://api.sablebolt.io/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_swap Create a swap (for an agent that controls the sending wallet) ~293
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | 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 |
| from | string | yes | asset slug you send, e.g. usdt-trc20 |
| fromAddress | string | yes | 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 |
| to | string | yes | asset slug to receive, e.g. btc |
| toAddress | string | yes | the receiving address for the `to` asset |
No output schema declared.
No examples provided.
get_limits Minimum and maximum ~58
Minimum and maximum amount for a route, in the asset you send.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | asset slug you send, e.g. usdt-trc20 |
| to | string | yes | asset slug you receive, e.g. btc |
No output schema declared.
No examples provided.
get_quote Live quote ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | decimal amount you send, as a string |
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
get_swap_status Swap status ~50
Status of one swap by id: stage (1 waiting … 5 done), deposit and payout addresses, amounts, both transaction hashes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | swap id from the status page URL |
No output schema declared.
No examples provided.
list_assets List assets ~35
Every asset the swap form knows, with slug, ticker, network, confirmations, extra-id name and whether it is available right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_routes List routes ~29
Every route with its own page (from/to slugs) and whether both sides are available right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
swap_page_link Swap page link (hand-off) ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
validate_address Validate an address ~49
Whether an address has the right format for an asset. Does not check who owns it or whether an exchange needs a memo.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| asset | string | yes | asset slug |
No output schema declared.
No examples provided.
How do I install the Sablebolt swaps MCP server?
Sablebolt swaps is a hosted endpoint at https://api.sablebolt.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.sablebolt.io
claude mcp add --transport http io-sablebolt-swaps 'https://api.sablebolt.io/mcp'
What is the Sablebolt swaps MCP server?
Sablebolt swaps is an MCP server listed in the public MCP registry as io.sablebolt/swaps. Account-free crypto swaps: assets, routes, limits, live quotes, address checks, swap status. This page covers its hosted endpoint (https://api.sablebolt.io/mcp).
Is the Sablebolt swaps MCP server safe to use?
Sablebolt swaps scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sablebolt swaps MCP server expose?
Sablebolt swaps exposes 8 tools: list_assets, list_routes, get_limits, get_quote, validate_address, and 3 more. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.
Does the Sablebolt swaps MCP server require authentication?
Its publisher declares no required credentials for Sablebolt swaps. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Sablebolt swaps MCP server still maintained?
Sablebolt swaps is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.