Index / MCP servers / Vurto Swap

Vurto Swap MCP server

Connect Vurto Swap and your agent gets 32 tools, among them check_access, check_access_challenge, check_analyze. It answers at https://swap.vurto.cc/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 24 September 2026; the last check, on 8 November 2026, succeeded.

Status
Answering
Tools
32
Reliability
4 of 4 checks
Response time
307 ms
Transport
streamable HTTP
Last checked
8 November 2026

Token swaps at the best net price on 9 EVM chains and Solana. No API key, non-custodial.

Description as the publisher wrote it.

The 32 tools Vurto Swap offers

ToolWhat it does
check_accessThe Check access of a paying wallet, the proof check_credits asks for (access), valid 24 hours. Hand here the signature of check_access_challenge with its nonce and message, unchanged. The challenge is consumed here, once, so the access goe
Inputs: wallet, nonce, message, signature, transaction
check_access_challengeOnly for check_credits (listing a payer's Checks by wallet); paying, analysing and reading one Check need only its id. The challenge of the Check access, of its own: the text says what the signature grants (read and use the paid Checks of t
Inputs: wallet, chainId
check_analyzeSpends ONE paid credit on the networks it paid: evmWallet on the EVM networks paid, solanaWallet on Solana if it was paid. Give a wallet for each family the credit paid (check_wallet_missing otherwise) and none for a family it did not (chec
Inputs: checkId, evmWallet, solanaWallet, wallet
check_buy_challengeStep one of buying a Check (owner, 12/11/2026: only a wallet that passes the free screening buys, so it signs first). The challenge of its own, scope buy: the text says this wallet pays for a Check and is screened before buying, valid 10 mi
Inputs: wallet, chainId
check_buy_proofHand here the signature of check_buy_challenge with its nonce and message, unchanged. The challenge is consumed once, the wallet goes through the free screening (OFAC, issuer freezes), and only if it passes it returns { buyProof (vcb_..., 1
Inputs: wallet, nonce, message, signature, transaction
check_chargeBuilds the USDC transfer of the Check price for the networks chosen (networks, from check_info checkNetworks: perNetwork each, never above maximum) from payer to the analysis fee wallet on chainId (any network of check_info networks), for t
Inputs: chainId, buyProof, payer, networks, checkId
check_creditsThe paid Checks of a paying wallet, newest first, 50 a page with nextCursor: unused credits (status paid), a reading in flight or interrupted (status running: call check_analyze again with its target to resume) and the analyses already run
Inputs: payer, access, cursor
check_infoThe paid Check of any wallet: price { maximum (dollars, one system variable, 1.99), perNetwork (the maximum divided by 6, down to the cent: 0.33), amount (= maximum, for older clients), currency }; the price of a Check is perNetwork times t
check_report_paymentHand the Check payment to the server once it is mined, by the Check id. The server reads it on-chain (the payer the charge names signed it, the network USDC reached the fee wallet, at least the price, after the charge, the mark) and reserve
Inputs: checkId, txHash
check_resultReads one Check by its id, as stored (status, target, seal, result, screening, networks, events). Never calls a paid provider. An unknown id gets check_not_found (404).
Inputs: checkId
destination_authorizeHand over the signature of destination_challenge. The server checks it is the paying wallet's signature over that exact challenge, for that receiver and chain, unexpired and unused, and then lets builds deliver to that receiver for 30 minut
Inputs: wallet, receiver, chainId, nonce, message, signature
destination_challengeDestination lock. A receiver different from the signing wallet is refused by swap_build, double_build and nn_build (403 destination_not_authorized) until the paying wallet signs an authorization for that exact address on that chain. This re
Inputs: wallet, receiver, chainId, chargeId, chargeTxHash
double_buildBuilds signable/sendable plans for BOTH legs of a Double Out or Double In swap — two ordinary swap_build calls under the hood, kept together for convenience. Returns { legA, legB }, each a full SwapPlan exactly like swap_build's. The two le
Inputs: chainId, wallet, legA, legB, maxSlippageBps
double_quoteCompares ranked routes for TWO swap legs at once — "Double Out" (one source token split into two destinations) or "Double In" (two source tokens converging on one destination). This exists because building a liquidity pool or matching a tar
Inputs: mode, chainId, wallet, legA, legB
invoice_analysis_payDo not use it on an invoice whose split.rule is "brackets" (created since 10/11/2026): its fee is inside the payment and already pays the analysis of both wallets, and the call is refused with analysis_included_in_fee (409). Without checks:
Inputs: id, payer, checks
invoice_createCreate a payment request: who receives, which token, how much, on which network. Returns invoice.id, invoice.label (INV-XXXX-XXXX, what people copy), invoice.url (share this, after paying the analysis charge if the invoice has one; it previ
Inputs: chainId, recipient, token, amount, memo, confidential
invoice_getRead an invoice by id (INV-XXXX-XXXX, with or without dashes): requested amount, token, network, receiver, status (open or paid), the paying transaction once paid, and received (the raw amount measured on-chain so far). Pending payments are
Inputs: id
invoice_payBuild the plan to pay an invoice from payer, with the token payer holds (default: the invoice token). Nothing is signed or sent here. Both wallets are screened first (payer_blocked, receiver_blocked); when the invoice has checks ["scorechai
Inputs: id, payer, tokenIn, slippageBps
invoice_report_analysis_paymentHand the analysis payment transaction to the server once it is mined. The server reads it on-chain: a direct USDC transfer (the USDC of the invoice network) from the invoice creator to the Vurto fee wallet, of at least analysis.amount, newe
Inputs: id, txHash, payer
invoice_report_paymentHand the payment transaction to the server, right after sending it. The server reads the transaction on-chain and measures what reached the receiver in the invoice token; the payer must be the signer and the transaction must be newer than t
Inputs: id, payer, txHash, method
nn_buildBuilds ONE signable/sendable atomic transaction executing every leg of an N:N basket through VurtoSwapRouter. Always re-quotes the whole basket fresh from chainId/inputLegs/outputLegs — there is no quoteId handoff for N:N, pass the same fie
Inputs: chainId, wallet, inputLegs, outputLegs, slippageBps
nn_quoteN:N — quotes a basket where N input tokens fund M output tokens in ONE atomic on-chain transaction. The backend runs a waterfall allocation deciding which input finances which output, then quotes the real tokenIn->tokenOut route for each re
Inputs: chainId, wallet, inputLegs, outputLegs, slippageBps
payout_batchPayroll and supplier payouts to many wallets in one batch, on Solana and on the nine EVM chains (those with loteSplit true in GET /v1/chains). EVM: up to 50 wallets, in a verified USD stablecoin (USDC, USDT, PYUSD, USDG, USD1) — the batch i
Inputs: chainId, token, payer, recipients, checks
payout_chargeStep 2 of a payout_batch with checks, on Solana or EVM. After signing and sending payout_batch's charge.transaction, hand its signature or hash here with the loteId and payer. The server verifies the charge on-chain, runs the paid analysis
Inputs: loteId, txHash, payer
payout_report_paymentHand one batch transaction to the server, right after sending it, with the invoiceIds that payout_batch listed for it. Each invoice is verified on-chain like any invoice payment (what reached that receiver); call again a few seconds later i
Inputs: txHash, payer, invoiceIds
payout_reusePreview which wallets in a batch (Solana or EVM) ran this analysis for this payer in the last 30 days: a hint, read with no network call; whether it comes from the history is decided when the charge is paid, by the movement measured then; e
Inputs: chainId, payer, recipients, checks, token
prepare_signingSynthesizes the local CLI signer invocation for one step of a swap_build plan. Does not call the Vurto backend — this only assembles the payload. You (the agent) do not need a private key and must never ask for one in chat: signing happens
Inputs: buildId, invoiceId, walletAddress, chainId, step
report_executionReports a completed swap, closing the loop. EVM transaction: pass wallet + txHash + quoteId; never report an approve step as an execution. EVM CoW signature: pass wallet + chainId + quoteId + signature; the server reloads the stored build a
Inputs: wallet, txHash, quoteId, chainId, signature, buildId
swap_buildBuild a signable/sendable plan for a swap. This is the tool that does the work — an agent that only knows this tool can execute a swap end to end. Quotes and builds the best route in one call when quoteId is omitted (recommended): a route w
Inputs: chainId, wallet, tokenIn, tokenOut, amount, amountRaw
swap_quoteCompare ranked routes across providers for a swap, without building or spending anything. Ranked by net value after gas and platform fee, not raw output, with ONE unit price for the output token across every route, so a friendlier price fee
Inputs: chainId, wallet, tokenIn, tokenOut, amount, amountRaw
swap_statusRe-checks a swap. EVM: pass wallet + executionId (the id from report_execution); for CoW ETH-flow this consults the orderbook and distinguishes order_expired_refundable from order_expired_refunded instead of trusting the registration receip
Inputs: wallet, executionId, signature
wallet_checkCheck any wallet (EVM 0x address or Solana base58, case-sensitive) before paying it or taking its money: OFAC SDN list on both families; on Solana also the issuer freeze of USDC and EURC (Circle), USDT (Tether), PYUSD and USDG (Paxos) and U
Inputs: wallet, chainId, checks

Add Vurto Swap to your AI client

Every block below points at https://swap.vurto.cc/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http vurto-swap https://swap.vurto.cc/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "vurto-swap": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://swap.vurto.cc/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "vurto-swap": {
      "url": "https://swap.vurto.cc/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "vurto-swap": {
      "type": "http",
      "url": "https://swap.vurto.cc/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "vurto-swap": {
      "url": "https://swap.vurto.cc/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "vurto-swap": {
      "serverUrl": "https://swap.vurto.cc/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "vurto-swap": {
      "url": "https://swap.vurto.cc/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Vurto Swap
version: 0.0.1
schema: v1
mcpServers:
  - name: Vurto Swap
    type: streamable-http
    url: https://swap.vurto.cc/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "vurto-swap": {
      "httpUrl": "https://swap.vurto.cc/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "vurto-swap": {
      "type": "http",
      "url": "https://swap.vurto.cc/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "vurto-swap": {
      "url": "https://swap.vurto.cc/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fswap.vurto.cc%2Fmcp&type=streamable_http&id=vurto-swap&name=Vurto%20Swap

Is Vurto Swap up right now?

It answered our last check on 8 November 2026 in 307 ms. Over 4 checks since 24 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Vurto Swap

Questions about Vurto Swap

How many tools does Vurto Swap have?

32, as returned by the server's own tools/list on 15 November 2026: check_access, check_access_challenge, check_analyze, check_buy_challenge, check_buy_proof, check_charge, check_credits, check_info, and 24 more.

Is Vurto Swap down?

It answered our last check on 8 November 2026 in 307 ms. Over 4 checks since 24 September 2026 it answered 4.

How do I add Vurto Swap to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://swap.vurto.cc/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Vurto Swap need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.cryptoconspiracy. Endpoint host: swap.vurto.cc. ARD identifier: urn:air:io.github.cryptoconspiracy:mcp:vurto-swap. First indexed 24 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.