MCP.so
登录

Xenarch — X402 MCP Server For Ai Agent Payments

@xenarch-ai

基本信息

分类

AI 与智能体

许可证

MIT

传输方式

stdio

作者

xenarch-ai

提交者

Em de Vries

关于 Xenarch — X402 MCP Server For Ai Agent Payments

x402 MCP server for AI agent payments. Gasless USDC micropayments on Base L2. Claude, Cursor, LangChain, CrewAI, AutoGen, LangGraph resolve HTTP 402 with no API keys. Non-custodial, settlement-provider-agnostic, 0% fee.

Xenarch — X402 MCP Server For Ai Agent Payments 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "xenarch": {
      "command": "npx",
      "args": [
        "-y",
        "@xenarch/agent-mcp"
      ]
    }
  }
}

Xenarch — X402 MCP Server For Ai Agent Payments 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。

概览

What is Xenarch — X402 Mcp Server For Ai Agent Payments?

Xenarch is a non-custodial x402 MCP server that enables AI agents (Claude, Cursor, LangChain, CrewAI) to pay for HTTP 402-gated APIs and content with USDC micropayments on Base L2. It requires no API keys, no subscriptions, and no credit card on file. The agent wallet never needs ETH; USDC is the only token it holds. Payments settle on-chain directly from the agent wallet to the publisher wallet with 0% Xenarch fee.

How to use Xenarch — X402 Mcp Server For Ai Agent Payments?

Configure your wallet by placing a private key in ~/.xenarch/wallet.json, then add the server to any MCP client (e.g., claude mcp add xenarch -- npx @xenarch/agent-mcp). Fund the wallet with USDC on Base — no ETH or other tokens needed. Optionally set the XENARCH_API_TOKEN environment variable to enforce managed caps and scope, and run xenarch agent login once to enable control-plane and merchant tools.

Key features of Xenarch — X402 Mcp Server For Ai Agent Payments

  • Non-custodial USDC micropayments on Base L2
  • Works on any host, not platform-locked
  • Agent needs only USDC — no ETH or gas coin
  • 0% Xenarch fee, no contract in money flow
  • 29 MCP tools for discovery, payments, control, and merchant operations
  • Open standard: x402 protocol plus pay.json

Use cases of Xenarch — X402 Mcp Server For Ai Agent Payments

  • AI agents paying for gated content per request
  • API monetization without subscriptions or API keys
  • Publishers charging per-request for their APIs
  • Agents from Claude, Cursor, LangChain, and CrewAI paying for HTTP 402–gated services
  • Machine-to-machine micropayments on Base L2

常见问题

1

What is the x402 protocol?

x402 is an open protocol for HTTP 402 Payment Required: a server returns HTTP 402 with a signed price and payment details, the client signs a USDC micropayment on Base L2, then retries the request with proof of payment. Xenarch automates both halves for AI agents.

2

Does the agent need ETH to pay?

No. The agent wallet only ever needs USDC on Base L2 — no ETH, no gas coin of any kind.

3

How are spending caps and scope enforced?

Set the `XENARCH_API_TOKEN` environment variable to an `xa_live_` agent key. The MCP server then refuses to pay without the token (fail‑closed), enforcing per‑tx, daily, and monthly caps, plus allow/deny scope rules. Caps can be managed via the dashboard at `dash.xenarch.dev`.

4

Is Xenarch custodial?

No. Xenarch never holds funds and there is no Xenarch contract between the agent and the publisher. Payments are direct USDC transfers (EIP‑3009) from the agent wallet to the publisher wallet.

5

What transports and auth methods does the server support?

The server uses a private key for wallet operations (set via `XENARCH_PRIVATE_KEY`), an optional API token for caps/scope control, and a SIWE session (via `xenarch agent login`) for control‑plane and merchant tools. All payment communication uses the x402 HTTP handshake.

评论

AI 与智能体 分类下的更多 MCP 服务器