Remote MCP · Endpoint

Swapper - XMR to USDC swaps MCP server

No. Swapper - XMR to USDC swaps answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://xmrtousdc.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.xmrtousdc/monero-swap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
528 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Swap Monero (XMR) <-> native USDC on Arbitrum One. No account or API key required. For AI agents.
Listing
From the official MCP registry (active).
Recent checks of Swapper - XMR to USDC swaps
CheckedResultHandshake
20 minutes agoHandshake completed528 ms
9 days agoHandshake completed348 ms
9 days agoHandshake completed342 ms
11 days agoHandshake completed330 ms
12 days agoHandshake completed335 ms
13 days agoHandshake completed366 ms
14 days agoHandshake completed328 ms
14 days agoHandshake completed538 ms
16 days agoHandshake completed333 ms
19 days agoHandshake completed348 ms
21 days agoHandshake completed367 ms
24 days agoHandshake completed333 ms
26 days agoHandshake completed424 ms
28 days agoHandshake completed337 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Swapper - XMR to USDC swaps and makes no claim about it beyond what these checks measured.