General Tools

metalend.tech

Provides tools for managing and monitoring MetaLend's yield rebalancer across lending protocols, including pool listings, balance tracking, bridge balances, and configuration.

x402 supported1 endpoint19 known toolsFirst detected August 28, 2026Last detected August 28, 2026

ENDPOINT 1

https://mcp.metalend.tech/mcp

No auth detected

MCP server metadata

Name: metalend-rebalancer
Version: 1.0.0

Capabilities

tools.listChangedresources.listChanged

Server instructions

Tools for MetaLend's rebalancer. Read-only discovery: list_pools, get_balances, get_bridge_balances, get_config, get_default_config, get_rewards, get_transaction_costs, get_token_info, get_withdrawal_version. Write flows (deposit, withdrawal, config update) always follow a prepare_* then submit_* pattern: prepare_* computes everything and returns data to sign, but never signs anything itself; submit_* takes a signature you produced yourself and relays it. This server never holds a private key. Deposits/withdrawals/config updates also require a wallet JWT from get_auth_challenge + submit_auth_verify, passed explicitly as `jwt` on every submit_* call (never cached server-side — this server holds no session state and cannot remember it for you). Reuse the same jwt across multiple write calls for that wallet within its own session instead of re-running get_auth_challenge/submit_auth_verify before every single write call — submit_auth_verify's response includes an expiresAt saying how long it's good for. SIWE, withdrawal, and config signatures are all chain-scoped for a smart-contract wallet — an EOA is unaffected, but a smart wallet must have (deployed, or via ERC-6492 counterfactual deployment) a valid signer on whichever chain(s) that tool's description says the signature is checked against (config in particular can require ALL of its domainIds' chains at once, not just one) — see each write tool's own description for specifics. Deposit signatures are the one exception: they only accept a raw EOA-style ECDSA signature — no smart-contract wallet support at all, not even ERC-6492 — so a smart-contract wallet must use prepare_deposit's `method: "approval"` instead. Every submit_* call is rejected with a 403 if `jwt` wasn't issued (via submit_auth_verify) for the exact `walletAddress` in that same call — always pass matching jwt/walletAddress pairs from the same auth flow. Full reference docs are in the metalend://docs resources.

Known tools 19

list_pools

List all pools MetaLend's rebalancer can deposit into: protocol (Aave, Morpho, Euler), chain, APY breakdown (native/rewards/total/net-of-fee), TVL, liquidity, and the signData (protocolId, poolAddress, domainId) needed to build a rebalancer config.

Inferred read-only

get_balances

Get a wallet's deployed rebalancer balances broken down per token, per chain, and per protocol/pool, including net earnings and blended APY.

Inferred read-only

get_bridge_balances

Get a wallet's in-transit USDC bridge balances (funds moving cross-chain toward a destination pool), including estimated completion time.

Inferred read-only

get_config

Get a wallet's current rebalancer configuration per token: which protocols/pools/chains are enabled, rebalance frequency, lifetime deposits/withdrawals/fees, and spending cap.

Inferred read-only

get_default_config

Get MetaLend's recommended default rebalancer configuration for a given token symbol (e.

Inferred read-only

get_rewards

Get a wallet's aggregated rewards/earnings across all reward sources (e.

Inferred read-only

get_transaction_costs

Get constant on-behalf deposit/withdraw gas costs and minimum deposit/withdraw amounts for a token, broken down per supported chain.

Inferred read-only

get_token_info

Get a token's on-chain metadata (display name, decimals, EIP-712 version) for a given chain.

Inferred read-only

get_withdrawal_version

Get the contract signing version string required for the EIP-712 domain data used when signing a withdrawal.

Inferred read-only

get_auth_challenge

Get a Sign-In-With-Ethereum challenge message for a wallet, required before any deposit/withdrawal/config-update tool.

Potential side effects

submit_auth_verify

Exchange a signed SIWE challenge message (from get_auth_challenge) for a JWT scoped to that wallet.

Potential side effects

prepare_deposit

Build everything needed to deposit into MetaLend's rebalancer, without signing anything.

Inferred read-only

submit_deposit

Submit a deposit to MetaLend's rebalancer — moves funds.

Inferred read-only

get_deposit_status

Poll the status of a deposit by trackingId (returned by submit_deposit).

Inferred read-only

prepare_withdrawal

Build the EIP-712 typed-data payload to sign for withdrawing from a specific pool, without signing anything.

Inferred read-only

submit_withdrawal

Submit a withdrawal from MetaLend's rebalancer — moves funds.

Inferred read-only

get_withdrawal_status

Poll the status of a withdrawal by trackingId (returned by submit_withdrawal).

Inferred read-only

prepare_config

Build the signing hash for updating a wallet's rebalancer configuration (which pools/protocols/chains it's allowed to move funds into), without signing anything.

Inferred read-only

submit_config

Submit a signed rebalancer configuration update.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.metalend-rebalancer]
url = "https://mcp.metalend.tech/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "metalend-rebalancer": {
      "type": "http",
      "url": "https://mcp.metalend.tech/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: metalend-rebalancer
Remote MCP URL: https://mcp.metalend.tech/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "metalend-rebalancer": {
      "url": "https://mcp.metalend.tech/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "metalend-rebalancer": {
      "type": "http",
      "url": "https://mcp.metalend.tech/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "metalend-rebalancer",
  "transport": "streamable-http",
  "url": "https://mcp.metalend.tech/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.