@lendwise/mcp

Unified view for lending markets. One standard.

MCP server for Lendwise — compare and optimize DeFi supply/borrow markets across Aave V3, Morpho and Compound V3 over live yield data.

It answers questions like "I have $1,000 to place in DeFi for the next 6 months — what are the best markets?" against real yield data, in about four tool calls.

Read-only. It compares markets; it never signs a transaction.

Install

Hosted (Streamable HTTP)

Point any MCP client at https://mcp.lendwise.fi/mcp — nothing to install. With Claude Code:

claude mcp add --transport http lendwise https://mcp.lendwise.fi/mcp

Local (stdio)

// claude_desktop_config.json / .mcp.json
{
  "mcpServers": {
    "lendwise": {
      "command": "npx",
      "args": ["-y", "@lendwise/mcp"]
    }
  }
}

No API key. The server holds no secrets — it speaks only HTTPS to the public Lendwise API.

Related MCP server: graph-lending-mcp

Tools

Why the TVL floor exists

find_best_markets defaults to minTvlUsd: 1_000_000. In a thin market a headline APY is mostly noise, and steering someone with $1k into one is the most plausible real-world harm this server can do. Lower it deliberately, not by accident.

Why get_market_history returns statistics, not just a series

A snapshot cannot tell a durable 6% from a 12% that is a reward programme ending next week. A 180-day standard deviation can. That is the number a 6-month decision actually turns on.

Configuration

Development

pnpm install
pnpm typecheck
pnpm test                                   # unit tests, hermetic
LENDWISE_INTEGRATION=1 pnpm test            # + live API tests
pnpm build

The one invariant to not break

The optimizer's contract is positional: we send apy: number[], it returns vault_index — an offset into the array we sent, not an id. If the array we build and the array we map back through ever disagree, the server confidently attributes a real allocation to the wrong market, and every number still looks plausible.

Order is therefore established exactly once, from the caller's productIds, and both directions run off that single array (buildApyVector → mapAllocations in src/core/optimizer.ts). It is pinned by unit tests in both directions. Do not "simplify" it into a lookup by APY value.

Rate limits

The upstream API allows 60 GraphQL req/min/IP and 10 optimizer req/min/IP. A 429 is surfaced as an explicitly retryable error carrying retryAfterSeconds — back off, don't retry-storm.

Not financial advice

Informational only. APYs are variable and historical yields do not predict future returns.

License

MIT