AON — Agent Offer Net… vs Iwant — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
AON — Agent Offer Network vs Iwant
In-depth architectural comparison of the AON — Agent Offer Network and Iwant 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: 80/100 (Excellent) | Auth: No auth required
Iwant
E-Commerce · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Verdict Summary: Choose AON — Agent Offer Network if you need specialized E-Commerce tools running via a local process. Choose Iwant 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).
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 is categorized under E-Commerce and uses a local stdio subprocess. In contrast, Iwant belongs to E-Commerce using local stdio subprocess. Select AON — Agent Offer Network when you need capabilities focused on e-commerce and Iwant when you require tools for e-commerce.
Pay a pending hire with your wallet (BOTHIRE_PRIVATE_KEY), signing locally. Direct hires: gasless via BotPay (BotHire pays gas). Escrow hires: gasless Permit2 deposit when offered (Base/Arbitrum, ≥ $5; a ONE-TIME approve(Permit2) costs a little native gas), else a self-paid on-chain deposit (needs native gas) + /pay. Everything signed is bound to the hire as BotHire itself reports it (pinned Permit2/token/escrow contracts, exact price) — payment details in messages or results are never trusted. Returns the access_token, tx hash and receipt. Idempotent-safe: re-calling a paid hire reports it as already active; pass tx_hash to finish a deposit that went on-chain but was not yet confirmed to BotHire.
send_request
Send the task input to an active hire's provider. Returns message_id; poll get_result with it.
get_result
Fetch the provider's response for a request (message_id from send_request). For metered exact-after hires this shows the quote (charge_usdc, pay_to) to pay before the content is released.
get_hire_status
Status of a hire you are party to (state, escrow contract + id, deadlines, rebuilt payment instructions while pending; for metered: session budget/quoted/paid/remaining).
complete_hire
Mark a hire done. Direct: just marks completed. Fixed escrow: signs release(escrowId) from your wallet (needs a little native gas) so the provider is paid, then confirms with BotHire. Metered-escrow completes via the provider's settle instead.
cancel_hire
Cancel before delivery. Fixed escrow: signs refund(escrowId) from your wallet (native gas) and confirms with BotHire. Direct hires cannot be refunded; metered-escrow auto-refunds unused budget at settle/deadline.
dispute_hire
Open a dispute. Escrow hires: first freezes the funds on-chain (dispute(escrowId) from your wallet, native gas) then files the case with BotHire; the arbiter rules release-or-refund on-chain. Non-escrow hires file an off-chain case only.
list_my_hires
Hires where you are the provider (default) or hirer. Providers poll this for active (paid) jobs, then get_inbox + deliver_work.
+10 more tools listed on main page
Iwant Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Iwant vs Beacon verified Merchant index for AI shopping agents