fry-x402-mcp

MCP server that exposes the fry.farm x402 agentic actions API as tools any MCP client (Claude Desktop, Claude Code, custom agents) can call.

• 15 pay-per-call endpoints on Algorand mainnet, priced $0.001–$0.01 in USDC (ASA 31566704): 3 DeFi/DePIN data feeds + 12 transaction actions (staking, LP farming, Genesis NFT mint, P2P offers, submit, status).

• Non-custodial: build tools return unsigned atomic groups. Your agent signs with its own wallet and submits via x402_submit. fry.farm never holds keys.

• No API keys, no accounts — x402 (v2, scheme exact) payment is the only auth. Payments verify and settle through the GoPlausible facilitator.

• Catalog-driven: tools are auto-generated at startup from the live, free /x402/catalog; x402_catalog_refresh picks up changes without a restart.

Quickstart

git clone https://github.com/Fry-Foundation/fry-x402-mcp.git
cd fry-x402-mcp
npm install && npm run build

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "fry-x402": {
      "command": "node",
      "args": ["/absolute/path/to/fry-x402-mcp/dist/index.js"],
      "env": {
        "AGENT_MNEMONIC": "your 25-word agent wallet mnemonic",
        "MAX_PAYMENT_USDC": "0.05"
      }
    }
  }
}

Generic MCP client (stdio)

Run node dist/index.js with the env vars below; speak MCP over stdio.

Multi-property example (Claude Desktop env)

"FRY_X402_BASES": "https://fry.farm,https://fry.market",
"ALGOD_TOKEN": "<node token if required>"

Related MCP server: algorand-mcp

Tools

Typical agent journey: x402_catalog → x402_staking_stake (returns unsigned group) → sign locally → x402_submit → x402_status.

Security notes — read before configuring

• AGENT_MNEMONIC is the agent's wallet, not your main wallet. Fund it with only what the agent should be able to spend (USDC for x402 fees + the amounts it will transact + ALGO for txn fees).

• The mnemonic is read once from the environment and held in process memory only — never logged, never written to disk, never sent anywhere. Payments are signed locally; only signed payment payloads leave the process.

• MAX_PAYMENT_USDC caps each x402 payment client-side. On-chain action amounts (stake sizes etc.) are separate — they are whatever your agent asks to build and sign.

• Every paid response includes the paymentReceipt header content when the facilitator settles the payment.

License

MIT © Fry Foundation