In-depth architectural comparison of the Graph Aave Mcp and Graph Polymarket 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 Aave Mcp
Finance & Fintech · Local stdio
Quality: 48/100 (Fair) | Auth: API Key required
Graph Polymarket Mcp
Finance & Fintech · Local stdio
Quality: 44/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Graph Aave Mcp if you need specialized Finance & Fintech tools running via a local process. Choose Graph Polymarket 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 Aave 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.
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 Aave Mcp is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Graph Polymarket Mcp belongs to Finance & Fintech using local stdio subprocess. Select Graph Aave Mcp when you need capabilities focused on finance & fintech and Graph Polymarket Mcp when you require tools for finance & fintech.
List all available Polymarket subgraphs with descriptions and key entities
get_subgraph_schema
Get the full GraphQL schema for a specific subgraph
query_subgraph
Execute a custom GraphQL query against any subgraph
get_market_data
Get market/condition data with outcomes and resolution status
get_global_stats
Get platform stats: market counts + real volume/fees/trades
get_account_pnl
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.