Supported Protocols
Kairu's protocol support is built on a single ProtocolAdapter interface — every protocol integration implements the same set of methods (getPosition, simulate*, getMarketData, getReserveDetails, getUserRewards, and so on). Aave is the first adapter. The interface is the reason new protocols are additive, not a rewrite.
Live today
Aave V3
Full support across:
Ethereum Polygon Arbitrum Optimism Base
GHO and sGHO balances are only queried on Ethereum Mainnet, since GHO does not exist on the other networks.
Kairu computes, for Aave positions:
- Per-asset LT-weighted health factor and per-asset liquidation price
- Aave-authoritative net APY (
(earnings − costs) / netEquity, not a naive spread) - E-Mode eligibility and uplift analysis
- Merit rewards, claimable per asset
- GHO / sGHO balance and staking APY (Ethereum Mainnet only)
- Recent supply / borrow / repay / withdraw transaction history
Roadmap
Compound V3
Same collateral/debt/liquidation-threshold model as Aave V3, making it the most direct next ProtocolAdapter implementation.
Morpho
Peer-to-peer matching sits on top of underlying pool mechanics comparable to Aave's — the risk-parameter shape (LTV, liquidation threshold) maps onto the same adapter methods.
Spark
A fork of Aave's own lending-pool design, which makes it the lowest-effort adapter to add once prioritized.
Why this matters for MCP
The moment a new protocol adapter lands, every MCP tool that returns position or market data starts returning cross-protocol results — get_position, simulate, get_market_data, and the rest — with no change to how your AI client is configured. The adapter interface is what makes "ask one question, get your whole DeFi exposure" possible without protocol-specific tool sprawl.