# xswap.to (remote · xswap.to)

Quote, create and track crypto swaps across hundreds of coins and networks. No account needed.

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `xswap.to`: 76/100 (this document), [markdown](https://verifymcp.io/servers/to-xswap-swap/xswap.md), [page](https://verifymcp.io/servers/to-xswap-swap/xswap)

## Channel facts

- Endpoint: `https://xswap.to/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 660 tokens (~165/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the xswap.to MCP server?

xswap.to is a hosted endpoint at https://xswap.to/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.

### Claude

```bash
claude mcp add --transport http to-xswap-swap 'https://xswap.to/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "to-xswap-swap": {
      "url": "https://xswap.to/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "to-xswap-swap": {
      "type": "http",
      "url": "https://xswap.to/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.to-xswap-swap]
url = "https://xswap.to/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "to-xswap-swap": {
      "type": "remote",
      "url": "https://xswap.to/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add to-xswap-swap --url 'https://xswap.to/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  to-xswap-swap:
    url: "https://xswap.to/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "to-xswap-swap": {
      "Transport": "http",
      "Url": "https://xswap.to/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add to-xswap-swap -t streamable-http -u 'https://xswap.to/mcp'
```

### Other

```json
{
  "mcpServers": {
    "to-xswap-swap": {
      "type": "http",
      "url": "https://xswap.to/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 76, +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.

### 2026-11-19 (score 75, +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.

### 2026-11-17 (score 74, +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.

### 2026-11-15 (score 73, +1)

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

### 2026-11-13 (score 72, +1)

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

### 2026-11-11 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 70)

First indexed and scored.

## MCP tools (4)

### `search_currencies` (~105 tokens)

Search currencies

Find coins and tokens by symbol, name or network and get their currency ids. Each id is one coin on one network: usdttrc20 is USDT on TRON, usdterc20 is USDT on Ethereum. Use the ids in get_quote and create_swap.

Input parameters:

- `limit` (integer): Most results to return.
- `query` (string, required): Symbol, name or network, for example "usdt", "usdt tron" or "solana".

### `get_quote` (~139 tokens)

Get a swap quote

Estimate how much the user receives for sending an amount, with the minimum and maximum for the pair. Network fees are already taken out of estimatedAmount. The rate floats, so the result is an estimate, not a promise. Show any warnings to the user.

Input parameters:

- `amount` (string, required): Amount of the from currency, as a decimal like "0.05".
- `from` (string, required): Currency to send. Currency id from search_currencies, for example btc, eth or usdttrc20.
- `to` (string, required): Currency to receive. Currency id from search_currencies, for example btc, eth or usdttrc20.

### `create_swap` (~244 tokens)

Create a swap

Create a swap order and get a one-time deposit address. Nothing moves until the user sends the deposit from their own wallet. Before calling, confirm with the user both currencies and their networks, the amount and the payout address. Afterwards tell the user to send exactly amount of the from currency, on its network, to depositAddress, to add depositExtraId as the memo or tag when it is set, and to keep trackUrl. Show any warnings to the user.

Input parameters:

- `address` (string, required): The user's wallet address that receives the to currency. It must be on the to currency's network.
- `amount` (string, required): Amount of the from currency the user will send, as a decimal like "0.05".
- `extraId` (string): Memo or tag for the payout address. Only when the receiving wallet needs one, such as an exchange account with a deposit tag.
- `from` (string, required): Currency to send. Currency id from search_currencies, for example btc, eth or usdttrc20.
- `to` (string, required): Currency to receive. Currency id from search_currencies, for example btc, eth or usdttrc20.

### `get_swap_status` (~64 tokens)

Get swap status

Current status of a swap by its id. Statuses: new, waiting (no deposit seen yet), confirming, exchanging, sending, finished, failed, refunded, verifying (paused for a check), expired.

Input parameters:

- `id` (string, required): Swap id that create_swap returned.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/to-xswap-swap/xswap#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 70

## Common questions

### What is the xswap.to MCP server?

xswap.to is an MCP server listed in the public MCP registry as to.xswap/swap. Quote, create and track crypto swaps across hundreds of coins and networks. No account needed. This page covers its hosted endpoint (https://xswap.to/mcp).

### Is the xswap.to MCP server safe to use?

xswap.to scores 76 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 xswap.to MCP server expose?

xswap.to exposes 4 tools: search_currencies, get_quote, create_swap, get_swap_status. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.

### Does the xswap.to MCP server require authentication?

No. We connected to xswap.to without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the xswap.to MCP server still maintained?

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

### What did VerifyMCP test on the xswap.to MCP server?

VerifyMCP ran 13 checks on xswap.to, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://xswap.to/mcp
- Website: https://xswap.to/developers/
- Changelog RSS feed: https://verifymcp.io/servers/to-xswap-swap/xswap.xml
- Changelog JSON feed: https://verifymcp.io/servers/to-xswap-swap/xswap/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/to-xswap-swap/xswap.json
- HTML version of this page: https://verifymcp.io/servers/to-xswap-swap/xswap
