Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Swapper - XMR to USDC swaps

REMOTE · XMRTOUSDC.XYZ

Swap Monero (XMR) <-> native USDC on Arbitrum One. No account or API key required. For AI agents.

Available components

+3 this week 84 Trust /100

Last scanned (3 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2143 tokens (~107/item across 20 items; 11 tools + 9 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Probed https://xmrtousdc.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xmrtousdc.xyz CN=YE1,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA384 62b6d5b72d160ba0e890db23be0d744f16f
SANs: xmrtousdc.xyz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of xmrtousdc.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
xmrtousdc.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://xmrtousdc.xyz/mcp Verified 200
http (plaintext) http://xmrtousdc.xyz/mcp HTTPS enforced 308 https://xmrtousdc.xyz/mcp
MCP tools · 11 exposed · ~1,597 tokens

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 →

Tool Tokens
create_support_ticket ~163

Stuck or failed swap, or a question: Support answers (get_support_ticket). Follow up with ticketId + replyToken. Never seed phrases or keys.

NameTypeReqDescription
categorystring–Short topic, e.g. "stuck", "refund". Default "agent".
detailstring––
messagestringyesWhat happened (sent what, when, what the user sees), or your question.
orderIdstring–ord_... of the affected order.
replyTokenstring–With ticketId.
sessionIdstring–Session UUID, if known.
ticketIdstring–Follow-up: an existing ticket.
walletAddressstring–Public address involved (sending wallet or destination).
NameTypeReqDescription
dataobject––
errorobject––
nextobjectyes–
okbooleanyes–
operationstringyes–
replyTokenstring|null––
statestring––
ticketIdstring|null––
userMessagestring––

No examples provided.

create_swap ~206

Step 2. Creates the order from get_quote's next.arguments (quoteId, plus to if the quote had none): one order per quote; moves no funds. An order cannot be cancelled; unfunded, it expires. Retry with the same arguments: the default idempotencyKey returns the same order. Fund once, only while payable is true: before signing deposit.payment, get_swap_status {orderId, payment} must return paymentCheck.safeToSend. Next: get_swap_status.

NameTypeReqDescription
detailstring––
idempotencyKeystring–Optional; default q_<quoteId>. Reuse on every retry. A custom key: a fresh random UUID per intent.
quoteIdstringyesFrom get_quote's next.arguments.
quoteIntentDigeststring–From next.arguments: create fails if the quote's terms differ.
tostring–Destination, only if the quote had none (next.missing). Never guess.
NameTypeReqDescription
dataobject––
depositobject|null––
destinationstring|null––
errorobject––
expectedReceiveobject|null––
fromQueueboolean––
idempotencyKeystring|null––
nextobjectyes–
okbooleanyes–
operationstringyes–
orderIdstring|null––
payableboolean––
payableReasonstring|null––
queueobject|null––
reconfirmRequiredboolean––
recoveredboolean––
replayedboolean––
statestring––
trackUrlstring|null––
userMessagestring––

No examples provided.

get_capabilities ~42

Optional. Chains, limits (provider minimum, USD), quote window, idempotency, validation rules, polling and the flow.

NameTypeReqDescription
detailstring––
NameTypeReqDescription
contractVersionstring––
dataobject––
errorobject––
nextobjectyes–
okbooleanyes–
operationstringyes–
statestring––
userMessagestring––

No examples provided.

get_funding_options ~146

Offline. How to get what the user sends: native USDC (not USDC.e) plus a little ETH for gas on Arbitrum One (u2x, default), or XMR in their own wallet (x2u). Pass from {chain, asset} (and amount) for one ordered checklist: quote, fund, re-quote (requoteOf).

NameTypeReqDescription
amountstring–Send amount from a quote, if known.
detailstring––
directionstring–u2x (default): the user sends USDC. x2u: XMR.
fromobject–Where the funds are now.
NameTypeReqDescription
checklistarray––
dataobject––
directionstring––
errorobject––
matchedboolean|null––
nextobjectyes–
okbooleanyes–
operationstringyes–
routeobject|null––
statestring––
userMessagestring––

No examples provided.

get_quote ~333

Step 1. Quote Monero (XMR) <-> native USDC on Arbitrum One; no account or API key. Creates no order. Quotes are estimates. Buy XMR ("get me 1 XMR"): {direction:"u2x", receiveAmount:"1"}. Sell XMR: {direction:"x2u", amount:"0.5"}. direction plus exactly one of amount (what the user sends) or receiveAmount (what they want). Pass to if known. Next: create_swap with next.arguments.

NameTypeReqDescription
agentKeystring–Optional key from request_agent_key.
amountstring–What the user SENDS (x2u: XMR, u2x: USDC). Digits and one dot; no commas or units.
basisstring–receiveAmount met by the estimate (default) or the provider minimum (if published).
chainstring–Default arbitrum (42161).
detailstring––
directionstring–Required. u2x: send USDC, get XMR. x2u: send XMR, get USDC.
receiveAmountstring–What the user wants to RECEIVE (u2x: XMR, x2u: USDC); needs direction.
requoteOfstring–Re-quote this quoteId's stored parameters; pass it alone.
tostring–Destination from the user: x2u an Arbitrum One 0x address, u2x a Monero address. Never guess.
NameTypeReqDescription
acceptUntilstring|null––
acceptWindowSecinteger|null––
agentKeyobject|null––
belowProviderMinimumboolean|null––
dataobject––
deltaobject|null––
destinationstring|null––
directionstring––
errorobject––
expiresInSecinteger|null––
guaranteedboolean––
minimumSwapUsdnumber|null––
nextobjectyes–
okbooleanyes–
operationstringyes–
prerequisitesobject|null––
quoteobject|null––
quoteIdstring|null––
statestring––
targetobject|null––
userMessagestring––

No examples provided.

get_support_ticket ~51

Support's answer on your ticket: status, awaiting, thread. Answers take minutes to hours.

NameTypeReqDescription
detailstring––
replyTokenstringyes–
ticketIdstringyes–
NameTypeReqDescription
awaitingstring|null––
dataobject––
errorobject––
nextobjectyes–
okbooleanyes–
operationstringyes–
repliesinteger|null––
statestring––
statusstring|null––
threadarray––
ticketIdstring|null––
userMessagestring––

No examples provided.

get_swap_status ~204

Step 3. waiting_for_funding -> deposit_detected -> swap_processing -> completed, or refunding / terminal_failure (outcome refunded, failed, expired). Long-poll with waitSec 25 and sinceState = the last state; repeat next until terminal. Call it before funding or showing a deposit again. payment: what your wallet will sign; sign only if paymentCheck.safeToSend.

NameTypeReqDescription
detailstring––
orderIdstringyesFrom create_swap or list_swaps.
paymentstring–Unsigned only: tx JSON {to,data,value,chainId}, an ethereum:/monero: URI, calldata or an unsigned raw tx. Never a signed transaction.
sinceStatestring–State from your previous call.
verifystring–Destination address (optional extra check).
waitSecinteger–Long-poll seconds for a change from sinceState (max 25; more is capped).
NameTypeReqDescription
attentionarray––
dataobject––
depositobject|null––
destinationstring|null––
errorobject––
evidenceobject|null––
mayChangeboolean––
nextobjectyes–
okbooleanyes–
operationstringyes–
orderIdstring|null––
outcomestring|null––
payableboolean––
payableReasonstring|null––
paymentCheckobject|null––
receivedobject|null––
receivedBelowMinimumboolean––
statestring––
statusstring|null––
terminalboolean––
trackUrlstring|null––
userMessagestring––
waitedobject|null––

No examples provided.

list_swaps ~117

Find orders when the orderId is lost (new chat, crash, unknown create outcome): pass the idempotencyKey create_swap used (default q_<quoteId>), or a sessionId. Read-only; addresses redacted; states can lag. Next: get_swap_status (live state, payable).

NameTypeReqDescription
detailstring––
idempotencyKeystring–The key create_swap used (default q_<quoteId>).
sessionIdstring–Session UUID, instead of idempotencyKey.
NameTypeReqDescription
dataobject––
errorobject––
lookupstring––
nextobjectyes–
notestring|null––
okbooleanyes–
operationstringyes–
ordersarray––
payableboolean––
payableReasonstring|null––
statestring––
userMessagestring––

No examples provided.

plan_swap ~132

Optional, offline. Checks a partial request (direction, amount or receiveAmount, to) and returns the next question for the user. Skip it when you have what get_quote needs.

NameTypeReqDescription
amountstring–What the user sends.
detailstring––
directionstring–u2x or x2u, as the user said it.
receiveAmountstring–What the user wants to receive.
tostring–Destination from the user: x2u an Arbitrum One 0x address, u2x a Monero address. Never guess.
NameTypeReqDescription
dataobject––
errorobject––
missingInputsarray––
nextobjectyes–
okbooleanyes–
operationstringyes–
questionobject|null––
statestring––
userMessagestring––
validationErrorsarray––

No examples provided.

request_agent_key ~105

Optional. Issues a key that identifies this agent; quotes made with it (get_quote agentKey) and their orders use the agent fee (swapper://trust). The operator sees the name and contact given.

NameTypeReqDescription
agentNamestring–Default: the MCP client's name (clientInfo).
contactstring–Optional; stored, shown to the operator.
detailstring––
purposestring–Optional; stored, shown to the operator.
NameTypeReqDescription
agentKeystring|null––
dataobject––
errorobject––
feePercentnumber|null––
keyIdstring|null––
nextobjectyes–
okbooleanyes–
operationstringyes–
standardFeePercentnumber|null––
statestring––
userMessagestring––

No examples provided.

submit_feedback ~98

Optional, after a swap: a rating 1-5 and a comment. The published average counts one rating per completed Swapper order; a comment marked publishable is shown after operator review.

NameTypeReqDescription
agentNamestring––
commentstring––
detailstring––
orderIdstring––
publishableboolean–May other agents read the comment?
ratingintegeryes–
NameTypeReqDescription
dataobject––
errorobject––
feedbackIdstring|null––
nextobjectyes–
okbooleanyes–
operationstringyes–
statestring––
userMessagestring––
verifiedSwapboolean––

No examples provided.

Install

How do I install the Swapper - XMR to USDC swaps MCP server?

Swapper - XMR to USDC swaps is a hosted endpoint at https://xmrtousdc.xyz/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 · xmrtousdc.xyz

# add to Claude Code
claude mcp add --transport http xyz-xmrtousdc-monero-swap 'https://xmrtousdc.xyz/mcp'
Common questions

What is the Swapper - XMR to USDC swaps MCP server?

Swapper - XMR to USDC swaps is an MCP server listed in the public MCP registry as xyz.xmrtousdc/monero-swap. Swap Monero (XMR) <-> native USDC on Arbitrum One. No account or API key required. For AI agents. This page covers its hosted endpoint (https://xmrtousdc.xyz/mcp).

Is the Swapper - XMR to USDC swaps MCP server safe to use?

Swapper - XMR to USDC swaps scores 84 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 Swapper - XMR to USDC swaps MCP server expose?

Swapper - XMR to USDC swaps exposes 11 tools: get_quote, create_swap, get_swap_status, get_funding_options, list_swaps, and 6 more. Their descriptions and schemas cost roughly 1,597 tokens of context every time the server is loaded.

Does the Swapper - XMR to USDC swaps MCP server require authentication?

No. We connected to Swapper - XMR to USDC swaps without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Swapper - XMR to USDC swaps MCP server still maintained?

Swapper - XMR to USDC swaps is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.