Side-by-Side Model Context Protocol Comparison
Graph Aave MCP vs PreReason MCP
In-depth architectural comparison of the Graph Aave MCP and PreReason 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: 63/100 (Good) | Auth: API Key required
PreReason MCP
Finance & Fintech · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Graph Aave MCP if you need specialized Finance & Fintech tools running via a local process. Choose PreReason 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: list_aave_chains, get_aave_reserves, get_aave_reserve.
Choose PreReason 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 (Freemium).
- You have access to required keys:
PREREASON_API_KEY. - Primary tools included: list_briefings, list_metrics, get_health.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Graph Aave MCP Tools (51)
list_aave_chains
Use this when the user asks which AAVE chains are supported, wants to pick a network, or needs to discover available AAVE deployments. Returns all supported chains with their subgraph IDs, protocol version (V2/V3), chain name, 30-day query volume, and key entities. Chains: Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Fantom (V3 + V2 legacy), plus AAVE Governance V3. Always call this first if chain is ambiguous.
get_aave_reserves
Use this when the user asks about AAVE lending markets, available assets, supply APY, borrow APY, TVL, utilization rate, collateral factors, or liquidation thresholds on a specific chain. Returns all active reserves sorted by total liquidity (TVL). RATE CONVERSION: liquidityRate and variableBorrowRate are in RAY units (1e27). Supply APY % = liquidityRate / 1e27 * 100. Borrow APY % = variableBorrowRate / 1e27 * 100. Amounts are in native token units — divide by 10^decimals for human-readable. Ideal for: 'What assets can I lend on Arbitrum?', 'What is USDC supply rate on Base?', 'Show me all AAVE V3 markets on Polygon'. SIZE: unfiltered this returns every active reserve (~28k tokens on Ethereum). Pass `symbols` for a named asset, or `compact: true` for rates only.
get_aave_reserve
Use this when the user asks about a specific AAVE asset in detail — e.g. 'Tell me everything about USDC on Ethereum AAVE', 'What are the WETH borrow parameters?', 'What is the liquidation threshold for WBTC collateral?'. Returns full reserve config: current rates, TVL, LTV, liquidation parameters, lifetime stats (total borrows/repayments/liquidations), and token addresses. RATE CONVERSION: divide liquidityRate / variableBorrowRate by 1e27 * 100 for APY %.
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).
Graph Aave MCP Configuration
PreReason MCP Configuration