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

Swaplume

https://api.swaplume.com

Registry code: 1760691a19420491

api record

Swaplume compares instant crypto exchanges and swaps at the best rate. Free, no API key.

Flow: get_quotes -> create_swap (returns a deposit address) -> get_swap every poll_after seconds until is_final.

endpoint
https://api.swaplume.com/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 Swaplume live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Swaplume free to use?
Yes — the hub reached it with no key and no payment.
What tools does Swaplume have?
6 tools: create_swap, validate_address, get_swap, get_quotes, list_currencies, list_providers.
Is Swaplume 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
503ms

last good check

priced tools
0

of 6 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 6 tools
2 open 4 never probed 2 of 6 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.

  • list_currencies open 1h ago

    Find assets and their networks. Each id ('ticker:network') works as from_asset or to_asset. contract: the token's address; extra_id_name: the asset uses a memo/tag.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 50,
          "maximum": 500,
          "minimum": 1,
          "description": "How many matches to list (count has the total)."
        },
        "search": {
          "type": "string",
          "maxLength": 64,
          "description": "Part of a ticker or name ('usd', 'doge')."
        },
        "ticker": {
          "type": "string",
          "maxLength": 32,
          "description": "Exact ticker ('usdt'): lists every network it's on."
        },
        "network": {
          "type": "string",
          "maxLength": 64,
          "description": "Network code or name ('trx', 'tron', 'solana')."
        },
        "provider": {
          "type": "string",
          "maxLength": 32,
          "description": "Only assets this exchange supports."
        }
      }
    }
    arguments 32 lines
  • list_providers open 1h ago

    The exchanges compared, with what each asks of a swap (email_required, refund_address_required...), kyc, ip_shared, ip_kept and notice.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • create_swap unknown never probed

    Create the swap and get the deposit address. No funds move here: the user then sends amount_from of from_asset to deposit_address (with deposit_extra_id as the memo, when present), as instructions says. Follow it with get_swap.

    mcp-tool

    {
      "type": "object",
      "$defs": {
        "RateType": {
          "enum": [
            "float",
            "fixed"
          ],
          "type": "string",
          "description": "`float`: the market rate when the deposit arrives. `fixed`: what you receive is locked when the swap is\ncreated, usually at a slightly worse rate."
        }
      },
      "required": [
        "from_asset",
        "to_asset",
        "address"
      ],
      "properties": {
        "email": {
          "type": "string",
          "maxLength": 254,
          "description": "The user's email, when the chosen quote has email_required."
        },
        "amount": {
          "type": "string",
          "pattern": "^\\d+(\\.\\d+)?$",
          "examples": [
            "0.1"
          ],
          "description": "Amount of from_asset the user sends. Pass this or amount_to."
        },
        "address": {
          "type": "string",
          "maxLength": 256,
          "minLength": 4,
          "description": "The user's payout address for to_asset, as they gave it."
        },
        "rate_id": {
          "type": "string",
          "maxLength": 1024,
          "description": "The chosen quote's rate_id (fixed rate)."
        },
        "extra_id": {
          "type": "string",
          "maxLength": 128,
          "description": "Memo/tag for the payout address, if the user's wallet needs one (XRP, XLM...)."
        },
        "provider": {
          "type": "string",
          "maxLength": 32,
          "description": "The chosen quote's provider. Without it: the best quote now, then the next best, among exchanges without a notice."
        },
        "to_asset": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Asset the user receives."
        },
        "amount_to": {
          "type": "string",
          "pattern": "^\\d+(\\.\\d+)?$",
          "examples": [
            "0.1"
          ],
          "description": "Exact amount of to_asset to receive, instead of amount (fixed rate only): the result's amount_from is what the user must send."
        },
        "rate_type": {
          "$ref": "#/$defs/RateType",
          "description": "'float' or 'fixed'. Default float, or fixed with amount_to."
        },
        "from_asset": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Asset the user sends."
        },
        "to_network": {
          "type": "string",
          "maxLength": 64,
          "description": "Network of to_asset, when its ticker is on several."
        },
        "from_network": {
          "type": "string",
          "maxLength": 64,
          "description": "Network of from_asset, when its ticker is on several."
        },
        "refund_address": {
          "type": "string",
          "maxLength": 256,
          "description": "The user's from_asset address, for a refund if the swap fails."
        },
        "idempotency_key": {
          "type": "string",
          "maxLength": 255,
          "description": "A UUID made once per swap. A retry with the same one and the same arguments returns the swap already made."
        },
        "refund_extra_id": {
          "type": "string",
          "maxLength": 128,
          "description": "Memo/tag for the refund address."
        }
      }
    }
    arguments 103 lines
  • validate_address unknown never probed

    Check a payout or refund address (create_swap runs the same check). valid: true; false: show reason to the user and ask again; null: this network's format isn't checked here. extra_id_name: the asset uses a memo/tag.

    mcp-tool

    {
      "type": "object",
      "required": [
        "asset",
        "address"
      ],
      "properties": {
        "asset": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Asset the address receives: 'usdt:trx', 'btc'..."
        },
        "address": {
          "type": "string",
          "maxLength": 256,
          "description": "The address, as the user gave it."
        },
        "network": {
          "type": "string",
          "maxLength": 64,
          "description": "Network of asset, when its ticker is on several."
        }
      }
    }
    arguments 25 lines
  • get_swap unknown never probed

    A swap's live status: waiting (for the deposit), confirming, exchanging, sending, finished, failed, refunding, refunded, expired, verifying (held for an ID check), action_required or unknown. instructions is the next step, for the user. Read it again after poll_after seconds, not sooner (each read asks the exchange), until is_final.

    mcp-tool

    {
      "type": "object",
      "required": [
        "swap_id"
      ],
      "properties": {
        "swap_id": {
          "type": "string",
          "pattern": "^sw_[a-z0-9]+$",
          "maxLength": 40,
          "minLength": 4,
          "description": "The id create_swap returned ('sw_...')."
        }
      }
    }
    arguments 15 lines
  • get_quotes unknown 1h ago

    Compare every exchange's offer for a swap, best first. In each quote, amount_to is what the user receives after all fees. With amount_to given instead of amount, quotes are sorted by amount_from, what the user sends. errors lists the exchanges that can't, and why (with their min/max when the amount is out of range); with no quote at all, limits has the widest min/max: suggest an amount inside it. savings_pct: how much more the best quote gives than the worst. Ask again after refresh_after seconds, not sooner.

    mcp-tool

    {
      "type": "object",
      "$defs": {
        "RateType": {
          "enum": [
            "float",
            "fixed"
          ],
          "type": "string",
          "description": "`float`: the market rate when the deposit arrives. `fixed`: what you receive is locked when the swap is\ncreated, usually at a slightly worse rate."
        }
      },
      "required": [
        "from_asset",
        "to_asset"
      ],
      "properties": {
        "amount": {
          "type": "string",
          "pattern": "^\\d+(\\.\\d+)?$",
          "examples": [
            "0.1"
          ],
          "description": "Amount of from_asset to send. Pass this or amount_to."
        },
        "to_asset": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Asset to receive, as from_asset."
        },
        "amount_to": {
          "type": "string",
          "pattern": "^\\d+(\\.\\d+)?$",
          "examples": [
            "0.1"
          ],
          "description": "Exact amount of to_asset to receive, instead of amount (fixed rate only)."
        },
        "providers": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "description": "Only ask these exchanges (ids from list_providers)."
        },
        "rate_type": {
          "$ref": "#/$defs/RateType",
          "description": "'float': the market rate when the deposit arrives, usually more. 'fixed': an amount guaranteed for a short time. Default float, or fixed with amount_to."
        },
        "from_asset": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Asset to send: 'btc', 'usdt:trx', or a ticker with from_network."
        },
        "to_network": {
          "type": "string",
          "maxLength": 64,
          "description": "Network of to_asset, when its ticker is on several."
        },
        "from_network": {
          "type": "string",
          "maxLength": 64,
          "description": "Network of from_asset, when its ticker is on several: a code or a name ('trx', 'tron', 'erc20')."
        }
      }
    }
    arguments 69 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 1760691a19420491.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1760691a19420491/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/1760691a19420491/badge.svg)](https://brick.blue/agent/1760691a19420491?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
100%

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.