In-depth architectural comparison of the Agent Discovery Mcp and Yolfi Agent 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
Agent Discovery Mcp
Finance & Fintech · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: other
Yolfi Agent
Finance & Fintech · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Agent Discovery Mcp if you need specialized Finance & Fintech tools running via a hosted cloud SSE transport. Choose Yolfi Agent if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agent Discovery Mcp when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: TEST_WALLET_KEY.
Minimal MCP server (250 lines TS) for ERC-8004 agent discovery + x402 payment. Three tools: findagentsbyskill (via 8004scan public API), getagentcard, callagentwithpayment using Coinbase's official x402-fetch. Direct EOA signing — no smart account, no bundler, no relay. Works with Claude Code, OpenClaw, Cursor, Cline. USDC on Base/Ethereum + testnets, MIT.
Yolfi Payments MCP lets AI coding agents register Yolfi workspaces, create crypto checkout payment links, configure webhooks, verify webhook signatures, and check payment status. Install with npx -y @yolfi/agent mcp.
Agent Discovery Mcp is categorized under Finance & Fintech and uses a remote streaming HTTP/SSE transport. In contrast, Yolfi Agent belongs to Finance & Fintech using local stdio subprocess. Select Agent Discovery Mcp when you need capabilities focused on finance & fintech and Yolfi Agent when you require tools for finance & fintech.