MetaLend
Server Details
Browse, deposit, withdraw & rebalance stablecoins on Aave, Morpho & Euler across major EVM chains.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- rabeles11/metalend-mcp
- GitHub Stars
- 0
- Server Listing
- MetaLend
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 19 tools
The prepare/submit pairs, get_config vs get_default_config, and get_balances vs get_bridge_balances all have explicitly delineated boundaries spelled out in their descriptions, so an agent can navigate them. However, several small helper tools (get_withdrawal_version, get_token_info, get_transaction_costs) sit close in purpose, and the sheer number of read tools targeting wallet/chain/token state creates some borderline overlap.
Names follow a consistent snake_case verb_noun/verb_object pattern throughout: get_*, list_*, prepare_*, submit_*. The auth pair (get_auth_challenge/submit_auth_verify) and status pair (get_deposit_status/get_withdrawal_status) reinforce predictable conventions with no mixed casing or stylistic drift.
19 tools is slightly above the ideal band for a single-purpose server, but every tool maps to a real step in the protocol's multi-phase flows (SIWE auth, EIP-712 prep+submit for config/deposit/withdrawal, status polling, balances, pools, rewards). Nothing appears redundant or trivially filler, so the count is defensible even if heavy.
The surface covers the full auth → prepare → submit → poll lifecycle for deposits, withdrawals, and config, plus reads for balances, pools, config defaults, rewards, and token/gas metadata. Gaps exist (no rewards-claim submission, no way to pre-check in-progress rebalances or refills, no transaction history), but these are backend limitations the descriptions explicitly acknowledge rather than agent-facing blind spots.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Leveraged-yield router on Morpho. List strategies, simulate, and build UNSIGNED txs.
Analyse crypto wallets (EVM, Solana, Bitcoin) and compare DeFi lending, borrowing and pool rates.
Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed.
Crypto yield data for AI agents: lending, savings, staking, borrowing & stablecoin rates. 21 tools.
Related MCP Servers
- FlicenseAqualityDmaintenanceComplete DeFi intelligence — Yield, Staking, Restaking, RWA, Perps, Gas Optimization & Contract Security. One answer, not raw data.17-
- AlicenseAqualityBmaintenanceSelf-custodial crypto portfolio and DeFi MCP server. Read balances and positions (Aave, Compound, Morpho, Uniswap V3, Lido, EigenLayer) across Ethereum, Arbitrum, Polygon, and Base, and prepare transactions for approval on a Ledger via WalletConnect.100203 npm4Business Source 1.1
- AlicenseNot gradedqualityBmaintenancePhosphor is a local stablecoin portfolio manager that exposes an MCP server, enabling AI agents to read balances, composition, and costs, and propose actions like consolidation or policy changes, with all execution gated by explicit human approval in the app window.1Functional Source , Version 1.1, MIT Future
- AlicenseAqualityBmaintenanceEnables AI agents and quantitative traders to query block-accurate DeFi telemetry across Morpho Blue, Ethena, Fluid, Sky, Euler V2, and Pendle V2, including stablecoin carry/arbitrage radar and pre-trade risk simulation. It provides atomic Multicall3 reads, post-trade utilization and APY slippage checks, cap headroom decoding, and Pendle TWAP/logit-curve analysis through REST and MCP-compatible endpoints.71MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.