Is com.aave/mcp up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.aave.com |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://mcp.aave.com/server-card |
| MCP server card (SEP-1649 location) | Published, valid. SEP-2127 shape; com.aave/mcp 1.0.0; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://mcp.aave.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 53 tools: cancel_order, get_aave_guide, get_apy_history, get_asset_history, get_chains, get_emode_categories, get_governance_proposal, get_hub_assets, get_hubs, get_interest_rate_model, get_market_history, get_markets, get_multichain_asset, get_order_status, get_pending_orders, get_position_items, get_proposal_payloads, get_proposal_votes, get_protocol_history, get_reserve_details, get_reserve_holders, get_risk_premium, get_safety_module, get_sgho_preview, get_sgho_vault, get_spoke_configs, get_started, get_swap_quote, get_swappable_tokens, get_transaction_processed, get_user_activity, get_user_positions, get_user_rewards, get_user_summary, get_user_summary_history, get_user_vote, get_vault_activity, get_vault_preview, get_vaults, get_wallet_balances, prepare_action, prepare_cancel_order, prepare_claim_rewards, prepare_liquidation, prepare_order, prepare_set_collateral, prepare_set_emode, prepare_sgho_action, prepare_stkgho_migrate, prepare_vault_action, preview_action, search_governance_proposals, submit_signed_order.
Its tools changed between 2026-09 and 2026-10:
- Added (13):
get_asset_history,get_interest_rate_model,get_market_history,get_multichain_asset,get_reserve_holders,get_risk_premium,get_safety_module,get_spoke_configs,get_vault_activity,get_vault_preview,get_vaults,get_wallet_balances,prepare_vault_action get_aave_guide: description, input schema changedget_sgho_vault: description changedget_user_summary: description changedprepare_stkgho_migrate: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.aave/mcp |
|---|---|
| Endpoint | https://mcp.aave.com |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt