mcpField
M
MetaLend

MetaLend

Remote
mcp.metalend.techFinance0Updated 3w ago

About MetaLend

MetaLend is a remote MCP server for stablecoin holders to compare yields and manage positions on Aave, Aave V4, Morpho, and Euler across EVM chains. It prepares transactions for wallet signing and never holds private keys.

Key features

  1. 01View live yields across protocols
  2. 02Track balances, APY, and rewards
  3. 03Deposit, withdraw, and rebalance positions
  4. 04Manage rebalancer settings
  5. 05Estimate transaction costs and minimum deposits
  6. 06Sign transactions in the user's wallet

Use cases

  1. 01Compare stablecoin yields across EVM chains
  2. 02Check wallet balances, blended APY, and pending rewards
  3. 03Deposit stablecoins into or withdraw them from pools
  4. 04Move funds from lower- to higher-yield pools

MCP support

As a remote MCP server, MetaLend exposes tools for yield discovery, portfolio monitoring, deposits, withdrawals, and configuration to MCP clients. Write operations return transaction data for wallet signing and relay the user's signed payload.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.metalend.tech/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

19

This tool takes no parameters.

Details

From the project README

MetaLend MCP

Your co-pilot for stablecoin yield — from research all the way to execution.

Browse, deposit, withdraw & rebalance stablecoin positions on Aave, Aave V4, Morpho & Euler. Track yields, balances, rewards & rebalancer settings across all major EVM chains.

MetaLend is a remote MCP server that turns your AI agent into both a yield analyst and a hands-on operator. Instead of manually comparing rates across lending protocols and chains, MetaLend scans the market for you: it monitors the best-paying pools for your specific stablecoins, highlights where you could earn a higher APY, and lets you act on it — deposit, withdraw, or rebalance — without leaving your agent.

No spreadsheets. No constant manual checking. No leaving money on the table.


Non-custodial by design

MetaLend never holds a private key and never signs anything itself.

Every deposit, withdrawal, or config change is computed by the server and handed back to you as a transaction to sign in your own wallet. The server then relays your signed payload. You stay in full custody at every step.


Install

Remote MCP server (Streamable HTTP):

https://mcp.metalend.tech/mcp
Cursor

Add to ~/.cursor/mcp.json (or a project .cursor/mcp.json):

{
  "mcpServers": {
    "metalend": {
      "type": "http",
      "url": "https://mcp.metalend.tech/mcp"
    }
  }
}
Claude Code
claude mcp add --transport http metalend https://mcp.metalend.tech/mcp
Claude Desktop / other clients

Point your client at the URL above using the HTTP (Streamable HTTP) transport.


What you can do

  • Access live rates — real-time yields across major protocols on multiple EVM chains
  • Track & alert — monitor market shifts, compare current positions, surface a better yield
  • Monitor portfolios — live balances, blended APY, and pending rewards for any public wallet address
  • Deposit & withdraw — move stablecoins into the best pools or pull them back out
  • Rebalance & configure — update which tokens and chains you track and your target allocation
  • Forecast actions — look up transaction costs and minimum deposit amounts before committing

Coverage

Protocols: Aave, Aave V4, Morpho, Euler

Chains: Multiple EVM chains, including Base, Ethereum, Polygon, Arbitrum, and Linea


Tools

Read-only discovery
ToolPurpose
list_poolsLive yields across protocols and chains
get_balancesWallet balances and blended APY across every chain and pool
get_bridge_balancesBalances relevant to cross-chain moves
get_rewardsUnclaimed reward incentives across your pools
get_configYour current rebalancer tracking preferences
get_default_configDefault rebalancer configuration
get_token_infoToken metadata and minimum deposit amounts
get_transaction_costsEstimated gas / transaction costs per chain
get_withdrawal_versionCurrent withdrawal contract version
get_deposit_status / get_withdrawal_statusStatus of a submitted deposit / withdrawal
Auth (wallet JWT)
ToolPurpose
get_auth_challengeGet a SIWE challenge to sign
submit_auth_verifyExchange the signed challenge for a wallet-scoped JWT
Write flows (prepare_* → sign → submit_*)
ToolPurpose
prepare_deposit / submit_depositMove stablecoins into a chosen pool
prepare_withdrawal / submit_withdrawalWithdraw stablecoins from a pool
prepare_config / submit_configUpdate rebalancer tokens, chains, and target allocation

prepare_* computes everything and returns data for you to sign; it never signs. submit_* relays a signature you produced yourself. The server holds no session state — the wallet JWT from get_auth_challenge + submit_auth_verify is passed explicitly on every submit_* call.


Use cases

  • Browse current stablecoin yields on Aave, Aave V4, Morpho, and Euler
  • Compare rates across Base, Ethereum, Polygon, Arbitrum, and Linea
  • Check a wallet's balances, blended APY, and pending rewards across every chain
  • Deposit stablecoins into a chosen pool
  • Withdraw stablecoins from a pool
  • Move funds from a lower-yield pool into a higher-yield one
  • Update rebalancer settings: which tokens and chains to track
  • Set a target allocation so positions follow the best available yield
  • Look up gas costs and minimum deposit amounts before moving funds
  • Track unclaimed reward incentives across your pools
  • Monitor a company treasury wallet across all chains in one view
  • Get notified when a better yield becomes available

Links


License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.