swap

Axnet Swap: An atomic, Request-First Solana execution layer for AI agents using Dual-Sign handshakes to eliminate prepayments and failed swaps.

CommunityDegradedNo sign-inGlobalFreeRead-only

What it can do

  • Prepare Swap: FIRST STEP. Initializes a swap and returns an HTTP 402 challenge. This tool provides the unsigned fee_tx and swap_tx. DO NOT call this tool again once you have the transactions. Instead,
  • Submit Swap: SECOND STEP. Finalizes the swap. Use this tool ONLY AFTER the user has signed the transactions provided by prepare_swap. Input: the signed Base64 strings for fee_tx and swap_tx.

What data it sees

Do you need an account

No: the server works without sign-in

Axnet Swap: An atomic, Request-First Solana execution layer for AI agents using Dual-Sign handshakes to eliminate prepayments and failed swaps.

Axnet is the first Solana swap protocol built specifically for autonomous agentic swarms. Unlike traditional swap interfaces that require active wallet connections and manual approvals, Axnet uses a Recursive Handshake Pattern to decouple swap intent from execution.

Key Features:

  • Atomic Reliability: Uses Dual-Sign transactions (Fee + Swap) ensuring either both execute or neither do—no more "stuck" funds or partial fills.
  • Stateless Execution: Agents don't need to maintain a persistent connection; the protocol uses the X-402-ID header to track intent through the signing lifecycle.
  • Agent-Native Security: Private keys never leave the agent's local environment. Axnet provides the "Challenge" transactions; the agent provides the signatures. *Deep Liquidity: Routed via Jupiter V6+ for optimal pricing across all Solana DEXs.

How to connect

How to connect swap to Claude

The server address to paste into Claude settings:

https://swap--axnet.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect swap to ChatGPT

The server address to paste into ChatGPT settings:

https://swap--axnet.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect swap to Cursor

The server address to paste into Cursor settings:

https://swap--axnet.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (2)

Raw names from tools/list. Only developers need these.

prepare_swapFIRST STEP. Initializes a swap and returns an HTTP 402 challenge. This tool provides the unsigned fee_tx and swap_tx. DO NOT call this tool again once you have the transactions. Instead, ask the user to sign them and then immediately call submit_swap.
submit_swapSECOND STEP. Finalizes the swap. Use this tool ONLY AFTER the user has signed the transactions provided by prepare_swap. Input: the signed Base64 strings for fee_tx and swap_tx.