Aave MCP
REMOTE · MCP.AAVE.COM · 2 COMPONENTS · SCANNED SEP 23
Official Aave MCP for V3 and V4 markets, positions, governance, and transaction preparation.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_signed_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 15076 tokens (~212/item across 71 items; 53 tools + 18 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 53 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Aave MCP server?
Aave MCP is a hosted endpoint at https://mcp.aave.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.aave.com
claude mcp add --transport http com-aave-mcp 'https://mcp.aave.com/'
{
"mcpServers": {
"com-aave-mcp": {
"url": "https://mcp.aave.com/"
}
}
} {
"servers": {
"com-aave-mcp": {
"type": "http",
"url": "https://mcp.aave.com/"
}
}
} [mcp_servers.com-aave-mcp] url = "https://mcp.aave.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-aave-mcp": {
"type": "remote",
"url": "https://mcp.aave.com/",
"enabled": true
}
}
} openclaw mcp add com-aave-mcp --url 'https://mcp.aave.com/' --transport streamable-http
mcp_servers:
com-aave-mcp:
url: "https://mcp.aave.com/" {
"McpServers": {
"com-aave-mcp": {
"Transport": "http",
"Url": "https://mcp.aave.com/"
}
}
} assistant mcp add com-aave-mcp -t streamable-http -u 'https://mcp.aave.com/'
{
"mcpServers": {
"com-aave-mcp": {
"type": "http",
"url": "https://mcp.aave.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Tool “get_market_history” rewrote its description, which is the text the model reads security
- Tool “get_spoke_configs” rewrote its description, which is the text the model reads security
- “get_vaults” added an optional parameter “cursor” cosmetic
- “get_spoke_configs” reworded the description of “spokeId” cosmetic
- “get_vault_activity” reworded the description of “window” cosmetic
- “get_spoke_configs” reworded the description of “hubId” cosmetic
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_aave_guide” rewrote its description, which is the text the model reads security
- Tool “get_sgho_vault” rewrote its description, which is the text the model reads security
- Tool “get_user_summary” rewrote its description, which is the text the model reads security
- Tool “prepare_stkgho_migrate” rewrote its description, which is the text the model reads security
- Schema quality: 11508 → 14941 ▼ functional
- New prompt “portfolio” functional
- New resource “aave-guide-safety-module” functional
- New resource “aave-guide-portfolio” functional
- New tool “get_asset_history” functional
- New tool “get_interest_rate_model” functional
- New tool “get_market_history” functional
- New tool “get_multichain_asset” functional
- New tool “get_reserve_holders” functional
- New tool “get_risk_premium” functional
- New tool “get_safety_module” functional
- New tool “get_spoke_configs” functional
- New tool “get_vault_activity” functional
- New tool “get_vault_preview” functional
- New tool “get_vaults” functional
- New tool “get_wallet_balances” functional
- New tool “prepare_vault_action” functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Probed https://mcp.aave.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aave.com | CN=WE1,O=Google Trust Services,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 553388f0021803511348b9257fd28237 |
| SANs: aave.com, mcp.aave.com, *.mcp.aave.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.aave.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aave.com. | present | 2371 | 13 | Verified |
| mcp.aave.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aave.com | Verified | 200 | |
| http (plaintext) | http://mcp.aave.com | HTTPS enforced | 301 | https://mcp.aave.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
preview_action Preview an action (simulate before executing) ~792
Simulate a supply/borrow/withdraw/repay against a wallet's position WITHOUT executing, on v3 or v4. Always do this before a borrow or a withdraw. Send only the arguments that apply: v4 takes 'reserveId'; v3 takes 'market' + 'token' + 'chainId'; 'max' is for withdraw and repay; 'native' works on both; 'enableCollateral' is v4 only. Both versions answer with 'healthFactorBefore' and 'healthFactorAfter'; v4 also returns net APY, risk premium, net collateral, net balance, projected earnings and both borrowing-power figures, each as a matching Before/After pair, plus 'rewardsAcquired' / 'rewardsAbandoned' when the action changes rewards. v3 has the two health factors and nothing else. Either version also returns 'warnings' when the action would not actually succeed - an error level there means the prepare step will refuse it, so fix the inputs rather than building it. Simulate first even when you intend to build immediately: this is the cheapest way to find out that an action cannot succeed, and it commits nothing. It reports the position's own limits and not token allowances, so a clean simulation says the position allows this, not that no approval step remains.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to simulate. |
| amount | string | – | Amount in MAIN units (e.g. '10.5'), never base units: 100000 base units of a 6-decimal token is '0.1', not '100'. Convert before sending if the user stated base units. Omit only if max=true. |
| chainId | number | – | v3 only: chain id (positive integer). |
| enableCollateral | boolean | – | v4 supply only: also enable as collateral. |
| market | string | – | v3 only: market pool address, from a get_markets row in this session. It cannot be recalled: an Aave pool address you already recognise belongs to another deployment (v2, or another chain) and is rej… |
| max | boolean | – | Withdraw/repay only: use the entire balance/debt. |
| native | boolean | – | Use the chain's native gas token instead of an ERC-20, on either version. Pass it whenever the action is in the native token, or the balance check below reads the wrapped ERC-20 balance and can refus… |
| reserveId | string | – | v4 only: the opaque reserveId, copied verbatim from a get_markets row or a get_position_items item in this session (e.g. 'MTo6MHg5NGU3...Ojo1') - it cannot be constructed or recalled, so fetch one be… |
| sender | string | yes | Sender wallet address (0x, 40 hex): the wallet that will sign, as the user named it in this session. If no wallet has been named, ask for it; never substitute a placeholder, which is rejected. |
| token | string | – | v3 only: underlying token address. |
| version | string | – | Optional: inferred from the reserve selector ('reserveId' is v4, 'market'+'token'+'chainId' is v3). Send it to be explicit, or if you somehow set both. |
No output schema declared.
No examples provided.
search_governance_proposals Search Aave DAO proposals ~261
Takes no 'version' argument (DAO governance is not per-market; Governance V3 is unrelated to Aave v3/v4 markets). List or search Aave DAO governance proposals. Filter by 'state' to answer "what is live right now" (state 'active') or "what is waiting to execute" (state 'queued'). Pass 'search' for full-text over title, author and description, ranked by relevance. Vote tallies are in AAVE.
| Name | Type | Req | Description |
|---|---|---|---|
| includeSummaries | boolean | – | Include each proposal's ~500-char summary (default false). Adds roughly 500 bytes per row, so ask for it when summarising a list rather than when looking one up. |
| limit | number | – | Max rows to return (1-100, default 20). |
| offset | number | – | Rows to skip, for paging (default 0). |
| search | string | – | Optional full-text query, e.g. 'GHO' or 'Chaos Labs'. Combines with 'state'. |
| state | string | – | Filter to one lifecycle state. 'active' is open for voting, 'queued' passed and waits out the timelock, 'executed' is done. Omit for every state. |
No output schema declared.
No examples provided.
submit_signed_order Submit a user-signed order ~91
No version argument: every order runs on the v4 backend. Relay an order the user already signed (quoteId + signature from prepare_order's PreparedOrder). State-changing: this posts the order. The server never signs.
| Name | Type | Req | Description |
|---|---|---|---|
| quoteId | string | yes | quoteId (the newQuoteId returned by prepare_order). |
| signature | string | yes | The user's EIP-712 signature (0x...). |
No output schema declared.
No examples provided.
What is the Aave MCP server?
Aave MCP is listed in the public MCP registry as com.aave/mcp. Official Aave MCP for V3 and V4 markets, positions, governance, and transaction preparation. This page covers its hosted endpoint (https://mcp.aave.com).
Is the Aave MCP server safe to use?
Aave MCP scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Aave MCP server expose?
Aave MCP exposes 53 tools: get_chains, get_markets, get_emode_categories, get_user_positions, get_position_items, and 48 more. Their descriptions and schemas cost roughly 13,676 tokens of context every time the server is loaded.
Does the Aave MCP server require authentication?
No. We connected to Aave MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Aave MCP server still maintained?
Aave MCP is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.