Nodegrove VRAM: can I run it?
by nodegrove.io in AI models & inference
Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU.
https://mcp.nodegrove.io/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 270 ms typical, 270 ms slowest 5%
- Last check
- 6 h ago
- Next check
- any minute now
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"nodegrove-vram-can-i-run-it": {
"type": "http",
"url": "https://mcp.nodegrove.io/mcp"
}
}
}6 tools
- can_i_run
Can this GPU run this open-weight LLM? Returns fits, tight or no, the memory split (weights, KV cache, overhead), a decode-speed ceiling, the longest context that fits and, on a no, every change that would make it fit: quantisation, KV cache, context, another card or a smaller mo
- what_fits
Which open-weight LLMs fit this GPU: every model in list_models checked at one quantisation and context, with a recommended everyday model (the biggest class that fits with room for context at conversational speed), the largest that fits, the best at Q8 and the first out of reach
- estimate_vram
How much memory an LLM needs: weights + KV cache + overhead at each quantisation (or one), at a given context, and the smallest common card class that holds each. Model: a name or id from list_models, any Hugging Face repo id, or its architecture (params_b, layers, kv_heads, head
- estimate_from_hf_repo
Reads any Hugging Face model repo's config.json and parameter count and estimates its memory: the attention layout found (standard, sliding-window, hybrid or latent), how much each 1,000 tokens of context costs, and weights + KV cache + overhead at every quantisation. For models
- list_models
The open-weight LLMs nodegrove.io has verified against their config.json (data version 2026-10-09): id, size, attention design, native context, licence, memory at Q4 with 8k context and each model's page.
- list_gpus
The GPUs and machines nodegrove.io covers: memory, the memory a runtime can use and bandwidth, from the makers' specs, with each one's page.
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 6 h ago | Passed | 200 | 270 ms |