Schema | Aave Liquidation MCP Server

Aave Liquidation MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`ETHEREUM_RPC_URL`	Yes	Your Ethereum RPC endpoint URL (e.g., from Alchemy, Infura, QuickNode, or your own node)
`HEALTH_FACTOR_THRESHOLD`	No	Health factor warning threshold	1.05

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
get_user_healthA	Get health factor and account data for a specific Ethereum address on Aave V3. Returns collateral, debt, and liquidation status.
analyze_liquidationB	Analyze a user position for liquidation opportunity. Returns detailed information including collateral assets, debt assets, risk level, and potential profit.
get_user_positionsB	Get detailed breakdown of a user collateral and debt positions across all Aave V3 assets.
get_aave_reservesB	Get list of all available reserves (assets) in Aave V3 protocol with their configuration.
get_asset_priceB	Get current price for a specific asset from Aave oracle.
get_protocol_statusB	Get general Aave V3 protocol status including current block number.
batch_check_addressesA	Batch check multiple Ethereum addresses for liquidation opportunities. Returns a summary of all addresses with their health status.
validate_addressB	Validate if a string is a valid Ethereum address format.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clumsynonono/aave-liquidation-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server