In-depth architectural comparison of the Graph Polymarket MCP and Graph Aave 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
Graph Polymarket MCP
Finance & Fintech · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Graph Aave MCP
Finance & Fintech · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Verdict Summary: Choose Graph Polymarket MCP if you need specialized Finance & Fintech tools running via a local process. Choose Graph Aave MCP 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 Graph Polymarket MCP when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: GRAPH_API_KEY, MCP_HTTP_PORT.
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: GRAPH_API_KEY.
Primary tools included: Aave V2 and V3 data across supported chains, Aave V4 hubs, spokes, reserves, positions, activities, and swap quotes, User health factor simulation and position analysis.
Graph Polymarket MCP is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Graph Aave MCP belongs to Finance & Fintech using local stdio subprocess. Select Graph Polymarket MCP when you need capabilities focused on finance & fintech and Graph Aave MCP when you require tools for finance & fintech.
Get a trader's P&L and performance metrics (winRate, profitFactor, maxDrawdown)
get_top_traders
Leaderboard ranked by PnL, winRate, volume, or profitFactor. Cross-refs Orderbook to flag rows where OB volume exceeds Beefy-tracked volume and surface OB-only traders absent from the leaderboard.
get_daily_stats
Daily volume, fees, trader counts, and market activity (1–90 days)
get_market_positions
Top holders for a specific outcome token with their P&L
get_user_positions
Current token positions. Cross-refs Orderbook: flags ⚠ orderbook-only entry when `totalBought=0` but OB volume exists, and ⚠ mixed entry when OB volume > 2× split collateral.
get_recent_activity
Unified chronological feed interleaving splits, merges, and redemptions with orderbook fills. Supports optional address filter.
get_orderbook_trades
Get recent order fills with maker/taker filtering
+23 more tools listed on main page
Graph Aave MCP Tools (6)
Aave V2 and V3 data across supported chains
Aave V4 hubs, spokes, reserves, positions, activities, and swap quotes
User health factor simulation and position analysis
Cross-chain liquidation risk scores, alerts, and summaries