Cleave for Agents: token swaps, cross-chain swaps and gas top-ups

fi.cleavePublished by cleave.fiOfficial publisherv1.0.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFinance

Overview

AI-generated overview

Cleave plans token swaps, cross-chain bridges and native-gas top-ups on six EVM chains, returning unsigned transactions for the user's own wallet to sign.

What you can do
  • Plan a same-chain swap, cross-chain swap or bridge, or a gas top-up, and get unsigned transactions to sign
  • Find a token by symbol or contract address, with decimals and a warning when it resembles a listed token
  • Track a planned or sent swap, bridge or gas order by chain, transaction hash and requestId
  • Get native gas (ETH, BNB or POL) for a wallet that holds USDC but no gas, returning one USDC authorization to sign
When to use it
Useful when a user wants to exchange tokens, move them between Ethereum, Arbitrum, Base, BNB Chain, Polygon or Optimism, top up gas from USDC, or check whether a transfer arrived. It has no routes on other chains.
Requirements
A remote MCP endpoint; no API key or environment variables are declared. The user needs a wallet on one of the six supported chains to sign the returned transactions or the USDC authorization.
Before you install
The tools move real funds: signing the returned transactions or the USDC authorization spends the user's tokens or USDC. Plans expire at a validUntil time and must be re-planned if stale, and some routes can go unfilled and only refund hours later. Use is subject to Cleave's Terms of Use and Privacy Policy.

Installation

In SourceWeft

  1. Open Cleave for Agents: token swaps, cross-chain swaps and gas top-ups in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/fi.cleave%2Fswap/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cleave-for-agents-token-swaps-cross-chai": {
      "type": "http",
      "url": "https://api.cleave.fi/mcp"
    }
  }
}

Tools

4

cleave_plan_swap

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 (exact or at least a minimum; 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.

ParametersamountrequiredwalletrequiredbuyTokenrequiredrecipientsellTokenrequiredtoChainIdfromChainIdrequiredmaxSlippageBps

cleave_track_swap

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.

ParameterstxHashchainIdrequestId

cleave_find_token

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 every candidate 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.

ParametersqueryrequiredchainIdrequired

cleave_get_gas

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 and a USDC amount, 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. Called again with the offer and the signature, 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 recipient gets at least the minimum or nothing moves; from another chain it gets the native coin at the minimum, else USDC on arrival if the arrival swap fails. An order not executed by its deadline is refunded to the refund address, or, if paid from another chain and not filled, refunded hours later. When the wallet already holds some gas, cleave_plan_swap plans a swap to the native coin.

ParametersofferamountwalletchainIdrefundTorecipientsignaturepayChainId

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.