_ registry / mcp streamable-http · checked 8h ago

xswap

https://xswap.to

Registry code: b298f7278abea940

api record

xswap.to swaps one cryptocurrency for another at a floating market rate through its exchange partner. Steps: search_currencies to get currency ids (each id is one coin on one network), get_quote for the estimate and the minimum, create_swap once the user has confirmed both currencies and networks, the amount and the payout address, then the user sends the deposit from their own wallet and get_swap_status follows the order. xswap.to never needs private keys or seed phrases. The final amount can differ a little from the quote.

endpoint
https://xswap.to/mcp
protocol
streamable-http ·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 it live, free and safe measured by this hub
Is xswap live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is xswap free to use?
Yes — the hub reached it with no key and no payment.
What tools does xswap have?
4 tools: get_swap_status, get_quote, create_swap, search_currencies.
Is xswap 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
291ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

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.

  • search_currencies open 8h ago

    Find coins and tokens by symbol, name or network and get their currency ids. Each id is one coin on one network: usdttrc20 is USDT on TRON, usdterc20 is USDT on Ethereum. Use the ids in get_quote and create_swap.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Most results to return."
        },
        "query": {
          "type": "string",
          "description": "Symbol, name or network, for example \"usdt\", \"usdt tron\" or \"solana\"."
        }
      }
    }
    arguments 19 lines
  • get_swap_status unknown 8h ago

    Current status of a swap by its id. Statuses: new, waiting (no deposit seen yet), confirming, exchanging, sending, finished, failed, refunded, verifying (paused for a check), expired.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Swap id that create_swap returned."
        }
      }
    }
    arguments 12 lines
  • get_quote unknown 8h ago

    Estimate how much the user receives for sending an amount, with the minimum and maximum for the pair. Network fees are already taken out of estimatedAmount. The rate floats, so the result is an estimate, not a promise. Show any warnings to the user.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to",
        "amount"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Currency to receive. Currency id from search_currencies, for example btc, eth or usdttrc20."
        },
        "from": {
          "type": "string",
          "description": "Currency to send. Currency id from search_currencies, for example btc, eth or usdttrc20."
        },
        "amount": {
          "type": "string",
          "description": "Amount of the from currency, as a decimal like \"0.05\"."
        }
      }
    }
    arguments 22 lines
  • create_swap unknown never probed

    Create a swap order and get a one-time deposit address. Nothing moves until the user sends the deposit from their own wallet. Before calling, confirm with the user both currencies and their networks, the amount and the payout address. Afterwards tell the user to send exactly amount of the from currency, on its network, to depositAddress, to add depositExtraId as the memo or tag when it is set, and to keep trackUrl. Show any warnings to the user.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to",
        "amount",
        "address"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Currency to receive. Currency id from search_currencies, for example btc, eth or usdttrc20."
        },
        "from": {
          "type": "string",
          "description": "Currency to send. Currency id from search_currencies, for example btc, eth or usdttrc20."
        },
        "amount": {
          "type": "string",
          "description": "Amount of the from currency the user will send, as a decimal like \"0.05\"."
        },
        "address": {
          "type": "string",
          "description": "The user's wallet address that receives the to currency. It must be on the to currency's network."
        },
        "extraId": {
          "type": "string",
          "description": "Memo or tag for the payout address. Only when the receiving wallet needs one, such as an exchange account with a deposit tag."
        }
      }
    }
    arguments 31 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b298f7278abea940.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b298f7278abea940/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b298f7278abea940/badge.svg)](https://brick.blue/agent/b298f7278abea940?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.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.