SWARM · MCP server

Use SWARM from Claude, Cursor or any MCP client

swarm-x402-mcp is an MCP server for SWARM's paid services. Add it to your MCP client and your agent can call them, paying per call in USDC on Base over x402. No account, no API key, and you are charged only when the service delivers.

Install#

Add this to your client's MCP configuration (Claude Desktop, Cursor and others use the same shape):

{
  "mcpServers": {
    "swarm": {
      "command": "npx",
      "args": ["-y", "swarm-x402-mcp"],
      "env": {
        "SWARM_WALLET_KEY": "0x…",
        "SWARM_MAX_USD": "1"
      }
    }
  }
}
Use a dedicated wallet holding only a few dollars of USDC on Base for SWARM_WALLET_KEY. Without a key the tools still list and quote; they explain the price and don't pay. SWARM_MAX_USD (default 1) makes the server refuse any call priced above it, before signing anything.

Tools#

Each tool calls SWARM's shop over the network and pays per call, so none is read-only; every tool declares that in its MCP annotations.

ToolPriceWhat you get
utilities$0.02UUIDs, hashes, base64, URL encoding, passwords, timestamps
code_health$0.05Static scan of a public GitHub repo: TODO debt, secret heuristics, hygiene
summary$0.75One-page brief on a topic, researched on the live web, sources linked
report$0.99Full researched Markdown report, sources linked
site_check$0.002Is a URL up? HTTP status, final URL, response time, TLS errors. For uptime monitoring and link checks
read_page$0.002A web page as clean, LLM-ready text: a median 97% fewer tokens than the raw HTML (15 pages measured)

How payment works#

Each call first reads SWARM's 402 quote without paying and checks two things: the network is Base mainnet, and the price is under your limit. Then it pays with the official x402 client. SWARM verifies the payment, does the work, and settles only if the work succeeded.

Source and docs: GitHub · npm · MCP Registry · machine-readable: openapi.json · .well-known/x402 · contact@swarm-agent.net