Nodegrove VRAM: can I run it?
REMOTE · MCP.NODEGROVE.IO · 2 COMPONENTS
Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU.
Available components
Last scanned (17 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 22 Oct 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1578 tokens (~263/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
- Server version: 1.1.3 → 1.1.4 functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Tool “list_models” rewrote its description, which is the text the model reads security
- Server version: 1.1.2 → 1.1.3 functional
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Tool “list_models” rewrote its description, which is the text the model reads security
- Server version: 1.1.1 → 1.1.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://mcp.nodegrove.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nodegrove.io | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f2f74a02fe841ab20e7b3c7dd8a3515b |
| SANs: nodegrove.io, mcp.nodegrove.io, *.mcp.nodegrove.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.nodegrove.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| nodegrove.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.nodegrove.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.nodegrove.io/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
can_i_run Can I run it? ~480
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 model. Model: a name or id from list_models, any Hugging Face repo id, or its architecture. GPU: a name or id from list_gpus, or vram_gb for any other card.
| Name | Type | Req | Description |
|---|---|---|---|
| active_params_b | number | – | Parameters read per token, billions, for a mixture-of-experts model read from Hugging Face (from its model card). Sets the speed ceiling. |
| apple_silicon | boolean | – | vram_gb is Apple unified memory; the GPU can use about 75% of it by default. |
| architecture | object | – | A model described by its config.json values instead of a name. |
| bandwidth_gb_s | number | – | Memory bandwidth from the maker's spec, GB/s, for a speed ceiling. |
| context | integer | – | Tokens held in context: prompt plus conversation. |
| gpu | string | – | A GPU from list_gpus (id or name, e.g. "rtx-4090", "4090" or "M4 Max"). |
| kv_cache | string | – | KV cache precision. fp16 is what most runtimes use; q8 halves the cache. |
| model | string | – | A model from list_models (id or name, e.g. "llama-3.3-70b" or "Llama 3.3 70B"), or any Hugging Face repo id (e.g. "Qwen/Qwen3-8B"), read live from its config.json. |
| quant | string | – | Weight quantisation: fp16 (FP16 / BF16), q8 (Q8_0), q6 (Q6_K), q5 (Q5_K_M), q4 (Q4_K_M), q3 (Q3_K_M). q4 is the common default. |
| vram_gb | number | – | Memory of a card not in list_gpus, GB. For a Mac, its unified memory with apple_silicon: true. |
No output schema declared.
No examples provided.
estimate_from_hf_repo Estimate VRAM from a Hugging Face repo ~198
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 nodegrove.io has not reviewed; anything the reader cannot model is listed in warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| active_params_b | number | – | Parameters read per token, billions, for a mixture-of-experts model read from Hugging Face (from its model card). Sets the speed ceiling. |
| context | integer | – | Tokens held in context: prompt plus conversation. |
| kv_cache | string | – | KV cache precision. fp16 is what most runtimes use; q8 halves the cache. |
| repo | string | yes | Hugging Face repo id, e.g. "Qwen/Qwen3-8B", or its huggingface.co URL. |
No output schema declared.
No examples provided.
estimate_vram Estimate VRAM ~312
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_dim).
| Name | Type | Req | Description |
|---|---|---|---|
| active_params_b | number | – | Parameters read per token, billions, for a mixture-of-experts model read from Hugging Face (from its model card). Sets the speed ceiling. |
| architecture | object | – | A model described by its config.json values instead of a name. |
| context | integer | – | Tokens held in context: prompt plus conversation. |
| kv_cache | string | – | KV cache precision. fp16 is what most runtimes use; q8 halves the cache. |
| model | string | – | A model from list_models (id or name, e.g. "llama-3.3-70b" or "Llama 3.3 70B"), or any Hugging Face repo id (e.g. "Qwen/Qwen3-8B"), read live from its config.json. |
| quant | string | – | Weight quantisation: fp16 (FP16 / BF16), q8 (Q8_0), q6 (Q6_K), q5 (Q5_K_M), q4 (Q4_K_M), q3 (Q3_K_M). Omit it for all 6. |
No output schema declared.
No examples provided.
list_gpus List GPUs ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Words to filter by, e.g. "qwen" or "24 GB". |
No output schema declared.
No examples provided.
list_models List models ~85
The open-weight LLMs nodegrove.io has verified against their config.json (data version 2026-10-16): id, size, attention design, native context, licence, memory at Q4 with 8k context and each model's page.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Words to filter by, e.g. "qwen" or "24 GB". |
No output schema declared.
No examples provided.
what_fits What fits my GPU? ~298
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. GPU: a name or id from list_gpus, or vram_gb for any other card.
| Name | Type | Req | Description |
|---|---|---|---|
| apple_silicon | boolean | – | vram_gb is Apple unified memory; the GPU can use about 75% of it by default. |
| bandwidth_gb_s | number | – | Memory bandwidth from the maker's spec, GB/s, for a speed ceiling. |
| context | integer | – | Tokens held in context: prompt plus conversation. |
| gpu | string | – | A GPU from list_gpus (id or name, e.g. "rtx-4090", "4090" or "M4 Max"). |
| quant | string | – | Weight quantisation: fp16 (FP16 / BF16), q8 (Q8_0), q6 (Q6_K), q5 (Q5_K_M), q4 (Q4_K_M), q3 (Q3_K_M). q4 is the common default. |
| vram_gb | number | – | Memory of a card not in list_gpus, GB. For a Mac, its unified memory with apple_silicon: true. |
No output schema declared.
No examples provided.
How do I install the Nodegrove VRAM: can I run it? MCP server?
Nodegrove VRAM: can I run it? is a hosted endpoint at https://mcp.nodegrove.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.nodegrove.io
claude mcp add --transport http io-nodegrove-vram-mcp 'https://mcp.nodegrove.io/mcp'
What is the Nodegrove VRAM: can I run it? MCP server?
Nodegrove VRAM: can I run it? is an MCP server listed in the public MCP registry as io.nodegrove/vram-mcp. Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU. This page covers its hosted endpoint (https://mcp.nodegrove.io/mcp).
Is the Nodegrove VRAM: can I run it? MCP server safe to use?
Nodegrove VRAM: can I run it? scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Nodegrove VRAM: can I run it? MCP server expose?
Nodegrove VRAM: can I run it? exposes 6 tools: can_i_run, what_fits, estimate_vram, estimate_from_hf_repo, list_models, list_gpus. Their descriptions and schemas cost roughly 1,437 tokens of context every time the server is loaded.
Does the Nodegrove VRAM: can I run it? MCP server require authentication?
No. We connected to Nodegrove VRAM: can I run it? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nodegrove VRAM: can I run it? MCP server still maintained?
Nodegrove VRAM: can I run it? is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.