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

@nodegrove/vram-mcp

v1.1.5

Published

MCP server: can this open LLM run on my GPU? VRAM, KV cache, speed ceilings and what would fit instead, with the exact math nodegrove.io uses. Any Hugging Face repo, any GPU.

Readme

@nodegrove/vram-mcp

An MCP server that tells your AI assistant whether an open-weight LLM fits your GPU, and what would fit instead. The arithmetic behind nodegrove.io, for any model on Hugging Face and any card. Free, read-only, no account or key.

Can my RTX 4090 run Llama 3.3 70B?

No: Llama 3.3 70B at Q4_K_M with 8,192 tokens of context needs 45.8 GB, and the RTX 4090 holds 22.8 GB after headroom. Short by 23 GB. The RTX 6000 Ada (48 GB) is within a whisker: with the KV cache at Q8 it needs 44.4 GB and fits.

Use it

Over stdio, with Node.js 20 or newer:

{
  "mcpServers": {
    "nodegrove-vram": {
      "command": "npx",
      "args": ["-y", "@nodegrove/vram-mcp"]
    }
  }
}

Or remotely, with nothing to install: https://mcp.nodegrove.io/mcp (Streamable HTTP, no authentication). Setup for Claude, Cursor, VS Code, ChatGPT and other clients: nodegrove.io/mcp.

Tools

| Tool | Answers | |---|---| | can_i_run | Fits, tight or no, the memory split, a speed ceiling, the longest context that fits, and on a no every change that would make it fit | | what_fits | Every model checked on one card, with a recommended pick, the largest that fits and the best at Q8 | | estimate_vram | Weights, KV cache and overhead at each quantisation, and the smallest common card that holds each | | estimate_from_hf_repo | Any Hugging Face repo, read from its config.json, with memory at every quantisation | | list_models, list_gpus | The models and cards, with their specs and pages |

Every figure is a stated formula over config.json values and the makers' specs, never a benchmark; speeds are ceilings. The method is at nodegrove.io/data.

Privacy

The local server sends nothing to Nodegrove. It contacts huggingface.co, and only when you ask about a repo there, to read that repo's public config.json.

Licence

MIT for the code; the bundled model and GPU data is CC BY 4.0. Credit Nodegrove (nodegrove.io).