fry-x402-mcp
MCP server exposing fry.farm's x402 API as tools, enabling non-custodial blockchain interactions with pay-per-call endpoints on Algorand.
README
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_refreshpicks 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.
| Env var | Required | Default | Purpose |
|---|---|---|---|
AGENT_MNEMONIC |
for paid tools | — | The agent's OWN Algorand wallet (25 words). Signs x402 payments and is the sender for built groups. Without it only free tools work. |
MAX_PAYMENT_USDC |
no | 0.05 |
Hard per-call spend ceiling; payment requirements above it are refused. |
ALGOD_URL |
no | public node | Override the Algorand node used by the payment client. |
ALGOD_TOKEN |
no | — | Sent as X-Algo-API-Token when set — required by token-gated nodes. |
FRY_X402_BASE |
no | https://fry.farm |
Single API base (unprefixed tool names). |
FRY_X402_BASES |
no | — | Comma-list of API bases for multi-property use. Each base's tools are prefixed with a short property tag (x402_farm_fleet, x402_market_market_collections, …) so multiple catalogs coexist without collisions. Takes precedence over FRY_X402_BASE. |
Multi-property example (Claude Desktop env)
"FRY_X402_BASES": "https://fry.farm,https://fry.market",
"ALGOD_TOKEN": "<node token if required>"
Tools
| Tool | Price | What it does |
|---|---|---|
x402_catalog |
free | Live catalog: endpoints, prices, params, payment requirements |
x402_catalog_refresh |
free | Re-fetch catalog, regenerate tools |
x402_fleet |
$0.01 | DePIN device-staking pool telemetry |
x402_farm |
$0.008 | Farming/pool analytics (pools, TVL, positions) |
x402_rewards |
$0.005 | FRY reward emission, daily budget, leaderboard |
x402_staking_stake / x402_staking_unstake / x402_staking_claim |
$0.01 | Build FryStaking V3 groups |
x402_lp_farm_stake / x402_lp_farm_unstake / x402_lp_farm_claim |
$0.01 | Build FryFarming groups |
x402_genesis_mint |
$0.01 | Build Genesis NFT mint group (currently paused on-chain) |
x402_p2p_create / x402_p2p_accept / x402_p2p_cancel |
$0.01 | Build P2P offer groups |
x402_submit |
$0.005 | Submit a signed group; waits ≤8 rounds |
x402_status |
$0.001 | Tx status by txid |
Typical agent journey: x402_catalog → x402_staking_stake (returns unsigned group) → sign locally → x402_submit → x402_status.
Security notes — read before configuring
AGENT_MNEMONICis 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_USDCcaps 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
paymentReceiptheader content when the facilitator settles the payment.
License
MIT © Fry Foundation
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.