torrentswap
Registry code: e0e2d8fb5af57a2a
TorrentSwap swaps crypto across chains without an account (BTC, ETH, SOL, USDT, USDC, TRX, ZEC, LTC, DOGE and more, on 17 networks). Fee: a flat 0.5%, already included in every quote.
Flow:
- endpoint
- https://torrentswap.com/mcp
- door code
- 0d6aef172c2d88e6
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is torrentswap live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is torrentswap free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does torrentswap have?
- 5 tools: list_assets, get_swap_status, validate_address, create_swap, get_quote.
- Is torrentswap safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_assets unknown never probed
List assets TorrentSwap can swap, with the id to use in get_quote, ticker, network and decimals. Any two different assets can be swapped. Optional query/network filters.
{ "type": "object", "properties": { "query": { "type": "string", "description": "Optional filter by ticker or name, e.g. \"usdt\" or \"bitcoin\"." }, "network": { "type": "string", "description": "Optional filter by network id or name, e.g. \"tron\" or \"solana\"." } }, "additionalProperties": false }arguments 14 linesget_swap_status unknown 1h ago
Check the progress of a swap by swapId: awaiting_deposit, confirming, exchanging, sending, completed, refunded, failed or expired.
{ "type": "object", "required": [ "swapId" ], "properties": { "swapId": { "type": "string", "description": "swapId returned by create_swap." } }, "additionalProperties": false }arguments 13 linesvalidate_address unknown never probed
Check that an address is valid for the network of an asset before creating a swap (checksums included). Returns the canonical form.
{ "type": "object", "required": [ "assetId", "address" ], "properties": { "address": { "type": "string", "description": "Address to check." }, "assetId": { "type": "string", "description": "Asset the address will receive, e.g. \"tron-usdt\". Determines the network." } }, "additionalProperties": false }arguments 18 linescreate_swap unknown never probed
Create a swap from a quoteToken returned by get_quote. Returns a one-time depositAddress, the exact amount to send, expiresAt and a swapId for tracking. Only call after the user confirmed the route and both addresses. The swap only happens when the user sends the funds. Repeating the call with the same quoteToken and addresses returns the same deposit address.
{ "type": "object", "required": [ "quoteToken", "destinationAddress", "refundAddress" ], "properties": { "quoteToken": { "type": "string", "description": "quoteToken of the chosen route (valid for about 2 minutes)." }, "refundAddress": { "type": "string", "description": "Address on the sell asset's network that receives a refund if the swap cannot complete." }, "destinationAddress": { "type": "string", "description": "Address that receives the bought asset, on the buy asset's network." } }, "additionalProperties": false }arguments 23 linesget_quote unknown 1h ago
Get live quotes for swapping one asset to another (cross-chain or same-chain). Returns routes ranked by amount received, each with a quoteToken, the executing protocol, expectedReceive, minimumReceived and estimated time. All fees (network, protocol and the 0.5% TorrentSwap fee) are included.
{ "type": "object", "required": [ "sellAssetId", "buyAssetId", "sellAmount" ], "properties": { "slippage": { "type": "number", "maximum": 5, "minimum": 0.1, "description": "Maximum slippage in percent. Default 1.5." }, "buyAssetId": { "type": "string", "description": "Asset to receive, e.g. \"ethereum-eth\". From list_assets." }, "sellAmount": { "type": "string", "description": "Amount to send as a decimal string in the sell asset's units, e.g. \"0.05\"." }, "sellAssetId": { "type": "string", "description": "Asset to send, e.g. \"bitcoin-btc\". From list_assets." } }, "additionalProperties": false }arguments 29 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ide0e2d8fb5af57a2a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e0e2d8fb5af57a2a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e0e2d8fb5af57a2a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.