npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lendwise/mcp

v0.1.4

Published

Unified view for lending markets, one standard — MCP server to compare and optimize DeFi supply/borrow across Aave, Morpho and Compound.

Readme

@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.

Tools

| tool | what it's for | | --- | --- | | list_market_universe | Every asset, chain and protocol that actually exists, with counts. Call this first — it's what stops an agent guessing a filter value that isn't there. | | find_best_markets | Current supply markets ranked by net APY. Filtering and sorting happen server-side. Defaults to ≥ $1M TVL. | | get_market_details | One market in full: protocol metadata, collaterals, APY split into base / rewards / fees. | | get_market_history | Daily net-APY series plus mean / stddev / min / max — the stability signal a long horizon needs. | | optimize_allocation | Split an amount across markets at a target diversification. Returns per-market amounts, blended APY, projected 6-month yield. |

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

| env var | default | purpose | | --- | --- | --- | | LENDWISE_API_URL | https://lendwise.fi | Point at http://localhost:3000 to develop against a local lendwise/web. | | LENDWISE_INTEGRATION | unset | Set to 1 to run the network integration tests. |

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 (buildApyVectormapAllocations 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