Skip to main content
The Xenarch MCP server is the npm package @xenarch/agent-mcp (version 1.3.1, MIT license). It runs over stdio and registers 103 tools. A few of them let an agent pay for content and APIs in USDC on Base. The rest manage the agent’s spend controls and the seller side of a Xenarch account. The server is listed in the official MCP Registry as io.github.xenarch-ai/xenarch-mcp.

What is an MCP server?

The Model Context Protocol (MCP) is an open standard for connecting AI agents to external tools. An MCP server exposes tools, and a client such as Claude Code or Claude Desktop calls them when a task needs them.

Tools by group

The tools reference documents the buying tools in full and lists every tool in the other groups.

How a payment works

  1. Check. xenarch_check_gate requests the URL. A Xenarch-gated URL answers with HTTP 402 and an x402 version 1 body that includes a gate_id, the payment requirements and a list of facilitators.
  2. Preflight. xenarch_pay compares the price with the local per-call cap (XENARCH_MAX_PAYMENT_USD, default $1). It then asks the Xenarch API whether your caps, scope rules and pause switch allow the payment.
  3. Sign. The server signs an EIP-3009 USDC transferWithAuthorization from the agent wallet to the seller’s wallet.
  4. Settle. It sends the signed authorization to the facilitators in the order the gate lists them. The first facilitator that succeeds submits the transfer on Base and pays the gas.
  5. Fetch. It requests the URL again with X-Xenarch-Gate-Id and X-Xenarch-Tx-Hash. The seller’s integration verifies the transfer and serves the content, which the tool returns with the transaction hash.
USDC moves from the agent wallet straight to the seller’s wallet. Xenarch has no contract in the payment path and charges no fee.

Limits

  • xenarch_pay and xenarch_pay_link refuse to pay until XENARCH_API_TOKEN holds an agent key. An agent without a key has no caps, so the server does not let it pay.
  • xenarch_pay pays only 402 responses that carry a Xenarch gate_id. A plain x402 402 from a server that does not use Xenarch reads as not gated.
  • Payments run on Base mainnet in USDC.

Supported clients

The README gives setup steps for Claude Code, Claude Desktop, Cursor and Cline. Any client that starts an MCP server over stdio works the same way.

Installation

Wallet, agent key and client configuration.

Tools reference

Inputs and outputs of each payment tool.