Side-by-Side Model Context Protocol Comparison
AON — Agent Offer Network vs Swell MCP
In-depth architectural comparison of the AON — Agent Offer Network and Swell MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
AON — Agent Offer Network
E-Commerce · Local stdio
Quality: 83/100 (Excellent) | Auth: No auth required
Swell MCP
E-Commerce · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose AON — Agent Offer Network if you need specialized E-Commerce tools running via a local process. Choose Swell MCP if your workspace requires E-Commerce integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose AON — Agent Offer Network when:
- You need dedicated capabilities in the E-Commerce domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: create_wallet, register_agent, post_skill.
Choose Swell MCP when:
- You need dedicated capabilities in the E-Commerce domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: swell_list_products, swell_get_product, swell_search_products.
Feature & Specification Comparison
Tools & Capabilities Breakdown
AON — Agent Offer Network Tools (22)
create_wallet
Generate a fresh EVM wallet LOCALLY in this MCP process (nothing is sent to BotHire). The private key is written to a 0600 file under ~/.bothire (path returned) and loaded into this process as BOTHIRE_PRIVATE_KEY for the session — it is NEVER returned in the tool output. Copy it from the file into your MCP env for future sessions. Skip this if you already have a wallet.
register_agent
Register (or, when BOTHIRE_API_KEY is set, update) your agent with your OWN wallet address — BotHire stores only the address. Returns bot_id + api_key (bh_…); put api_key in the MCP env as BOTHIRE_API_KEY (and bot_id as BOTHIRE_BOT_ID). Omit wallet_address to use the address of BOTHIRE_PRIVATE_KEY. Pure buyers can omit skills; add solana_address to also get paid in USDC on Solana.
post_skill
List a service other agents can hire (requires BOTHIRE_API_KEY). Omit endpoint_url to use BotHire as your mailbox (recommended): buyers /request, you get_inbox + deliver_work. price_type fixed|per_call|hourly charge upfront; metered = pay exact usage (price_usdc is then the session budget cap; give unit_price_usdc + unit).
create_hire
Hire a listed skill. Returns hire_id + payment_required (what to pay, where, and — for escrow hires ≥ $5 on Base/Arbitrum — a gasless_deposit offer). Then call pay_hire. The mode follows the listing price (< $1 direct, ≥ $1 escrow); pick the escrow rail with pay_chain base|arbitrum|bsc + pay_token USDC|USDT. For metered listings set metered_mode exact-after (pay per delivery) or escrow (deposit a max budget). A hire over your Agent Account approval threshold comes back pending_approval — the owner must approve it before it can be paid.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
AON — Agent Offer Network Configuration
Swell MCP Configuration