# Cleave for Agents: token swaps, cross-chain swaps and gas top-ups (remote · api.cleave.fi)

Swap, bridge and get gas on 6 EVM chains. Each plan states its outcome before you sign. No API key.

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

## Components

- remote · `api.cleave.fi`: 68/100 (this document), [markdown](https://verifymcp.io/servers/fi-cleave-swap/api.md), [page](https://verifymcp.io/servers/fi-cleave-swap/api)

## Channel facts

- Endpoint: `https://api.cleave.fi/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-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 400, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 52/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1757 tokens (~439/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**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 24% 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 current MCP spec version (2026-07-28).

## Install

### How do I install the Cleave for Agents: token swaps, cross-chain swaps and gas… MCP server?

Cleave for Agents: token swaps, cross-chain swaps and gas… is a hosted endpoint at https://api.cleave.fi/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 fi-cleave-swap 'https://api.cleave.fi/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fi-cleave-swap": {
      "url": "https://api.cleave.fi/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fi-cleave-swap": {
      "type": "http",
      "url": "https://api.cleave.fi/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fi-cleave-swap]
url = "https://api.cleave.fi/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add fi-cleave-swap --url 'https://api.cleave.fi/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fi-cleave-swap:
    url: "https://api.cleave.fi/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fi-cleave-swap": {
      "Transport": "http",
      "Url": "https://api.cleave.fi/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fi-cleave-swap -t streamable-http -u 'https://api.cleave.fi/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fi-cleave-swap": {
      "type": "http",
      "url": "https://api.cleave.fi/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-05 (score 68, +1)

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

### 2026-11-04 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “cleave_find_token” rewrote its description, which is the text the model reads
- [security] Tool “cleave_get_gas” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 396 → 439

### 2026-11-03 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “cleave_get_gas” rewrote its description, which is the text the model reads
- [security] Tool “cleave_plan_swap” rewrote its description, which is the text the model reads

### 2026-10-31 (score 66, +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-10-29 (score 65, +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-10-28 (score 64, +3)

- [security improvement] HSTS header: fail → pass

### 2026-10-27 (score 61, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 61)

First indexed and scored.

## MCP tools (4)

### `cleave_plan_swap` (~409 tokens)

Plan a swap, bridge or gas top-up

Plans a token swap on one chain, a cross-chain swap or bridge, or a native-gas top-up on Ethereum, Arbitrum, Base, BNB Chain, Polygon or Optimism, and returns unsigned transactions for the given wallet to sign. It fits when the user wants to exchange tokens, move them between these chains, or get ETH, BNB or POL for gas. It sends nothing and moves no funds. The answer leads with blocking notices and warnings, then gives the route's outcome kind (an exact amount or one that can vary; with a swap on arrival, the token, else a named fallback; where a transfer can go unfilled, a refund of the bridged token on the source chain hours later), every third-party cost except network gas, the expected time, validUntil and the calls in signing order. A blocking notice returns no calls; a warning, or a recipient other than the wallet, sets requiresConfirmation, and the connection's settings can turn either into a refusal. Calls sent after validUntil are stale: they can revert or, on some routes, end in a refund hours later. Amounts are decimal strings in token units; tokens are listed symbols or contract addresses; the recipient defaults to the wallet. Limits set in the connection (a pinned wallet, a per-plan USD cap, listed tokens only) bound every argument. For an ambiguous symbol, cleave_find_token lists the candidates; after sending, cleave_track_swap reports progress. A wallet with no gas can get it with cleave_get_gas.

Input parameters:

- `amount` (string, required): A decimal amount in token units
- `buyToken` (string, required): A listed symbol or a contract address
- `fromChainId` (integer, required)
- `maxSlippageBps` (integer)
- `recipient` (string)
- `sellToken` (string, required): A listed symbol or a contract address
- `toChainId` (integer)
- `wallet` (string, required)

### `cleave_track_swap` (~190 tokens)

Track a planned swap or transfer

Reports the status of a swap, bridge or gas top-up that was planned with cleave_plan_swap and then sent, or ordered with cleave_get_gas: its state (for example pending, in flight, delivered, refund pending or refunded), what arrived against the plan and on which chain, and the next action or when to check again. It takes the chain and transaction hash, plus the plan's requestId when known, or for a gas top-up the requestId alone; a transaction to a contract outside Cleave's published list is reported as such. It fits when the user asks whether such a transfer arrived, and before any re-send, because re-sending a plan that is still in flight can pay twice. It reports states only and returns no transactions.

Input parameters:

- `chainId` (integer)
- `requestId` (string)
- `txHash` (string)

### `cleave_find_token` (~144 tokens)

Find a token's contract address

Finds a token by symbol or contract address on Ethereum, Arbitrum, Base, BNB Chain, Polygon or Optimism and returns its address, decimals and whether it is on Cleave's token list, with a flag when it resembles a listed token. A symbol shared by several listed tokens returns up to ten candidates by address instead of picking one. An unlisted token is found only by its address and comes back flagged, without a name or symbol. It fits before cleave_plan_swap when the user names a token by symbol and the address is unknown.

Input parameters:

- `chainId` (integer, required)
- `query` (string, required): A symbol or a contract address

### `cleave_get_gas` (~450 tokens)

Get native gas with USDC

Gets native gas (ETH, BNB or POL) on Ethereum, Arbitrum, Base, BNB Chain, Polygon or Optimism for a wallet that holds USDC on Ethereum, Arbitrum, Base, Optimism or Polygon but has no gas to send transactions. Called with the paying chain, the receiving chain, the recipient, a USDC amount and the paying wallet (without it the offer has nothing to sign), it returns an offer: the fee, the minimum native amount, the deadline, the order and one USDC authorization for the wallet to sign; signing costs no gas. An offer needs 2 to 50 USDC (at least 5 USDC for gas on Ethereum) that covers the fee, a recipient that accepts the native coin and is not a token contract, and, for a cross-chain order, the paying wallet or a refundTo on the paying chain; otherwise, or while the route is paused, no offer is returned and the answer says why. Called again with the offer, the signature and the same wallet, it passes the signed order to Cleave's relayer, which executes it through a contract made for that one order, and returns a requestId for cleave_track_swap. On one chain the order swaps the USDC to the native coin for the recipient; from another chain it bridges the USDC and swaps it on arrival, delivering USDC instead if that swap fails. An authorization not used by its deadline expires and takes nothing. An order paid from another chain whose bridge transfer is not filled is usually refunded to the refund address on the paying chain within hours; until then, or if that USDC is worth less than sweeping it costs, cleave_track_swap shows it as refund_pending. When the wallet already holds some gas, cleave_plan_swap plans a swap to the native coin.

Input parameters:

- `amount` (string): A decimal amount in token units
- `chainId` (integer)
- `offer` (string)
- `payChainId` (integer)
- `recipient` (string)
- `refundTo` (string)
- `signature` (string)
- `wallet` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 68
- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 66
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 65
- 2026-10-29: 65
- 2026-10-28: 64
- 2026-10-27: 61
- 2026-10-26: 61

## Common questions

### What is the Cleave for Agents: token swaps, cross-chain swaps and gas… MCP server?

Cleave for Agents: token swaps, cross-chain swaps and gas… is an MCP server listed in the public MCP registry as fi.cleave/swap. Swap, bridge and get gas on 6 EVM chains. Each plan states its outcome before you sign. No API key. This page covers its hosted endpoint (https://api.cleave.fi/mcp).

### Is the Cleave for Agents: token swaps, cross-chain swaps and gas… MCP server safe to use?

Cleave for Agents: token swaps, cross-chain swaps and gas… scores 68 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 Cleave for Agents: token swaps, cross-chain swaps and gas… MCP server expose?

Cleave for Agents: token swaps, cross-chain swaps and gas… exposes 4 tools: cleave_plan_swap, cleave_track_swap, cleave_find_token, cleave_get_gas. Their descriptions and schemas cost roughly 1,193 tokens of context every time the server is loaded.

### Does the Cleave for Agents: token swaps, cross-chain swaps and gas… MCP server require authentication?

No. We connected to Cleave for Agents: token swaps, cross-chain swaps and gas… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Cleave for Agents: token swaps, cross-chain swaps and gas… MCP server still maintained?

Cleave for Agents: token swaps, cross-chain swaps and gas… 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.

## Links

- Remote endpoint: https://api.cleave.fi/mcp
- Website: https://cleave.fi/
- Changelog RSS feed: https://verifymcp.io/servers/fi-cleave-swap/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/fi-cleave-swap/api.json
- HTML version of this page: https://verifymcp.io/servers/fi-cleave-swap/api