Remote MCP · Endpoint

Vurto Swap MCP server

No. Vurto Swap answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://swap.vurto.cc/mcp

The last check completed an MCP handshake.

Registry name
io.github.cryptoconspiracy/vurto-swap
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
561 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Token swaps at the best net price on 9 EVM chains and Solana. No API key, non-custodial.
Listing
From the official MCP registry (active).
Recent checks of Vurto Swap
CheckedResultHandshake
53 minutes agoHandshake completed561 ms
2 days agoHandshake completed173 ms
4 days agoHandshake completed330 ms
5 days agoHandshake completed182 ms
7 days agoHandshake completed154 ms
8 days agoHandshake completed215 ms
9 days agoHandshake completed425 ms
11 days agoHandshake completed219 ms
13 days agoHandshake completed244 ms
15 days agoHandshake completed219 ms
17 days agoHandshake completed154 ms
18 days agoHandshake completed127 ms
19 days agoHandshake completed126 ms
20 days agoHandshake completed203 ms
21 days agoHandshake completed158 ms
21 days agoHandshake completed172 ms

The last 16 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 Vurto Swap and makes no claim about it beyond what these checks measured.