MCP server for analyzing Aave liquidation opportunities on Ethereum mainnet
Server has 8 tools with consistent naming (verb_noun pattern: get_*, analyze_*, validate_*) and basic descriptions. All tools are READ_ONLY, reducing risk. However, descriptions are generic (avg ~80 chars, below 194-char baseline), lack WHEN/WHY context, and parameter descriptions are minimal. Schemas are present but sparse, most parameters have only type and description, no constraints (enums, ranges, patterns). No output schemas documented. Error handling is absent, tools will fail silently on invalid addresses or network errors with no recovery guidance. Composition is reasonable (8 focused tools), but batch_check_addresses lacks pagination despite accepting arrays.
Analyze a user position for liquidation opportunity. Returns detailed information including collateral assets, debt assets, risk level, and potential profit.
Batch check multiple Ethereum addresses for liquidation opportunities. Returns a summary of all addresses with their health status.
Get list of all available reserves (assets) in Aave V3 protocol with their configuration.
Get current price for a specific asset from Aave oracle.
Get general Aave V3 protocol status including current block number.
Get health factor and account data for a specific Ethereum address on Aave V3. Returns collateral, debt, and liquidation status.
Descriptions lack WHEN/WHY context and are below baseline (avg 80 chars vs 194-char baseline). E.g., 'Get health factor and account data' does not explain when to call this vs analyze_liquidation or when it's a prerequisite.
No output schemas documented. LLMs cannot plan downstream calls or extract fields. E.g., what fields does analyze_liquidation return? What is the structure of collateral/debt arrays?
batch_check_addresses accepts array of up to 20 addresses but has no pagination or limit parameters. If results exceed context window, no way to fetch next page.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Get detailed breakdown of a user collateral and debt positions across all Aave V3 assets.
Validate if a string is a valid Ethereum address format.
No error handling or recovery guidance. Tools will fail on invalid addresses, network timeouts, or missing data with no actionable error messages. E.g., 'Invalid address' vs 'Invalid address: must be 42 hex chars starting with 0x. Try validate_address() first.'
Parameter descriptions are minimal. 'address' param appears in 5 tools but descriptions vary ('Ethereum address to check', 'Ethereum address to analyze', 'Ethereum address to query'). No format constraints (must be 42 hex chars, checksummed, etc.).