Aave MCP
v1.0.0Official Aave MCP for V3 and V4 markets, positions, governance, and transaction preparation.
Endpoint health
online- Last checked
- 11/20/2026, 5:18:21 AM
- Latency
- 292 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.aave%2Fmcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.aave/mcp": {
"url": "https://mcp.aave.com/"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Cancel an order
cancel_order
No version argument. Cancel an open order. Two routes: pass 'signature' (signed over what prepare_cancel_order returned) to relay a gasless cancellation - state-changing, and the route an intent order takes; omit 'signature' entirely for the on-chain route, which returns the cancel transaction for the user to sign and send, the route an order that went on chain (a native-token sell) takes. The server never signs.
Schema valid · SHA-256 eb5517273cde…
View input schema
{ "type": "object", "properties": { "orderId": { "type": "string", "description": "The order id (from submit_signed_order's receipt, get_order_status or get_pending_orders)." }, "signature": { "type": "string", "description": "The user's cancellation signature (0x...) over prepare_cancel_order's typed data. Omit the argument entirely to get the on-chain cancel transaction instead." } }, "required": [ "orderId" ], "additionalProperties": false }Get APY history
get_apy_history
Historical supply or borrow APY for a reserve over time, on v3 or v4. Returns a time-series of {date, apyPct}, where apyPct is a percent ('3.32' means 3.32%). Each point is an average over its sampling interval, and the interval widens with the window (hourly for 'day', coarser above that), so a series is not directly comparable to the instantaneous rate from get_reserve_details. Use get_markets first for the reserveId (v4) or market+token (v3). When comparing v3 against v4 for the same asset (a migration decision), read the history on both sides: a spot-rate gap can be one side's momentary spike.
Schema valid · SHA-256 41a4bcdd2643…
Connections
streamable-http
https://mcp.aave.com