swap
Registry code: f3ea967f609c8a6f
Buy EMC with USDT (TRC20), no account needed. Flow: get_swap_config for the limits/rate → buy_emc with the USDT amount and your EMC address → send the EXACT returned amount to the deposit address (one-way, no refunds) → poll get_order_status by token until 'notified'. cancel_order drops an unpaid order.
- endpoint
- https://swap.emercoin.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 swap live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
- Is swap free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does swap have?
- 4 tools: buy_emc, get_order_status, cancel_order, get_swap_config.
- Is swap 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 99.2%· all time 99.2%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- buy emc coins with usdt
- check swap order status
- get swap rate and limits
- cancel an unpaid swap order
- takes → gives
- data → data, payments
- tools
- 2 reads1 changes data1 moves money
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
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.
get_swap_config reads open 24h ago
Return the current order denominations and fixed rate for buying EMC with USDT. `allowed_amounts` is the exact set of USDT values buy_emc accepts (fixed denominations, not a free range) — pick one of these; `min_usdt`/`max_usdt` are its bounds and emc_per_usdt is the rate (EMC you receive = amount_usdt × emc_per_usdt). Call this first to choose a valid amount for buy_emc. Read-only — it neither creates nor changes an order. `support_email` is the operator contact for manual cases (e.g. an order on aml_hold or a late/mismatched payment).
{ "type": "object", "title": "get_swap_configArguments", "properties": {} }arguments 5 linesbuy_emc moves money unknown never probed
Open an order to buy EMC with USDT (TRC20) and get back a shared TRON `deposit_address` plus the EXACT `amount_usdt` to send. This does NOT move funds: you then transfer that exact figure (it is your order's matching tag) to the deposit address; on confirmed payment, EMC (amount_usdt × rate) is delivered to your address automatically. Keep the returned `token` and poll get_order_status until 'notified'; to abandon before paying, call cancel_order. One-way — a wrong amount cannot be matched and is NOT refunded. By default each call opens a NEW order; pass a stable `idempotency_key` to make retries return the same order. Use get_swap_config first to pick a valid amount.
{ "type": "object", "title": "buy_emcArguments", "required": [ "amount_usdt", "destination_emc_address" ], "properties": { "amount_usdt": { "type": "number", "title": "Amount Usdt", "description": "USDT to pay; must be one of the allowed denominations from get_swap_config (currently 5 or 10)", "exclusiveMinimum": 0 }, "idempotency_key": { "type": "string", "title": "Idempotency Key", "default": "", "description": "optional: a stable string you choose; retrying buy_emc with the same key + address + amount returns the SAME order instead of opening a new one (use it so a retry after a timeout doesn't create a duplicate)" }, "destination_emc_address": { "type": "string", "title": "Destination Emc Address", "description": "your EMC address to receive EMC (legacy 'E…' or bech32 'em1…')" } } }arguments 27 linesget_order_status reads unknown never probed
Return the current status of a buy_emc order by its `token`: the status, the exact amount, the EMC amount and destination address, and the `emc_txid` once delivered. Use this to poll after buy_emc — status progresses awaiting_payment → confirmed → emc_delivered → notified (done). Read-only; to cancel an unpaid order use cancel_order instead.
{ "type": "object", "title": "get_order_statusArguments", "required": [ "token" ], "properties": { "token": { "type": "string", "title": "Token", "description": "opaque order handle returned by buy_emc; pass it back unchanged" } } }arguments 14 linescancel_order changes data unknown never probed
Cancel a still-unpaid buy_emc order by its `token`, expiring it now and freeing its slot ahead of the TTL. Use this only before you pay; once a payment is in flight or confirmed it is too late and this errors. A payment sent after cancellation matches nothing and is NOT refunded. To only inspect an order without changing it, use get_order_status.
{ "type": "object", "title": "cancel_orderArguments", "required": [ "token" ], "properties": { "token": { "type": "string", "title": "Token", "description": "opaque order handle returned by buy_emc; pass it back unchanged" } } }arguments 14 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 idf3ea967f609c8a6f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f3ea967f609c8a6f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f3ea967f609c8a6f?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.