Skip to main content
Glama

Server Details

Browse, deposit, withdraw & rebalance stablecoins on Aave, Morpho & Euler across major EVM chains.

Ownership verified

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
88.9% over 61 days
Last Tested
Transport
Streamable HTTP
URL
Repository
rabeles11/metalend-mcp
GitHub Stars
0
Server Listing
MetaLend

TDQS

A4.2/5.0

Scored across 19 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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.

  1. 2 tool updates
    • Changedprepare_config1 field changed
      • changedInput schema / properties / protocolIds / description
        Previous value: -"0=Aave, 1=Morpho, 2=Euler — one entry per poolAddresses/domainIds entry, from list_pools' signData.protocolId. Pass only the exact set of (domainId, protocolId, poolAddress) pools you intend to allow, with no duplicate entries. Max 200 entries."New value: +"0=Aave, 1=Morpho, 2=Euler, 3=AaveV4 — one entry per poolAddresses/domainIds entry, from list_pools' signData.protocolId. Pass only the exact set of (domainId, protocolId, poolAddress) pools you intend to allow, with no duplicate entries. Max 200 entries."
    • Changedsubmit_config1 field changed
      • changedInput schema / properties / protocolIds / description
        Previous value: -"0=Aave, 1=Morpho, 2=Euler — one entry per poolAddresses/domainIds entry, from list_pools' signData.protocolId. Pass only the exact set of (domainId, protocolId, poolAddress) pools you intend to allow, with no duplicate entries. Max 200 entries."New value: +"0=Aave, 1=Morpho, 2=Euler, 3=AaveV4 — one entry per poolAddresses/domainIds entry, from list_pools' signData.protocolId. Pass only the exact set of (domainId, protocolId, poolAddress) pools you intend to allow, with no duplicate entries. Max 200 entries."
  2. 19 tool updates
    • First observedget_auth_challenge
    • First observedget_balances
    • First observedget_bridge_balances
    • First observedget_config
    • First observedget_default_config
    • First observedget_deposit_status
    • First observedget_rewards
    • First observedget_token_info
    • First observedget_transaction_costs
    • First observedget_withdrawal_status
    • First observedget_withdrawal_version
    • First observedlist_pools
    • First observedprepare_config
    • First observedprepare_deposit
    • First observedprepare_withdrawal
    • First observedsubmit_auth_verify
    • First observedsubmit_config
    • First observedsubmit_deposit
    • First observedsubmit_withdrawal

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    Self-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.
    100
    84 npm
    4
    Business Source 1.1
  • A
    license
    Not graded
    quality
    A
    maintenance
    Phosphor 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.
    480 npm
    1
    BSD 3-Clause
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.