Skip to content

Nodegrove VRAM: can I run it? MCP server

io.nodegrove/vram-mcpnodegrove.iostreamable-httpv1.1.5Scanned

Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU.

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Nodegrove VRAM: can I run it? MCP server can do

The Nodegrove VRAM: can I run it? MCP server is published by nodegrove.io, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: can_i_run, what_fits, estimate_vram and list_models), but cannot delete data. 2 tools only read.

1 tool reads private data (estimate_from_hf_repo); 3 tools bring in text other people can write (can_i_run, estimate_vram and estimate_from_hf_repo).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.1.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • can_i_runCan this GPU run this open-weight LLM?Reads text others write1 finding

    Why it is in this group

    • The name "can_i_run" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "can_i_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "can_i_run" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • estimate_vramHow 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_modelsThe open-weight LLMs nodegrove.io has verified against their config.json (data version 2026-11-03): id, size, attention design, native context, licence, memory at Q4 with 8k contex…1 finding

    Why it is in this group

    • The name "list_models" says "list": a word for reading.
    • The description's first verb is "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "list_models" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_models" says "list": a word for reading.

      What this check looks for
    Description, as the server wrote it
    The open-weight LLMs nodegrove.io has verified against their config.json (data version 2026-11-03): id, size, attention design, native context, licence, memory at Q4 with 8k context and each model's page.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • what_fitsWhich 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 fo…1 finding

    Why it is in this group

    • The description's first verb is "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "what_fits" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • estimate_from_hf_repoReads 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe name "estimate_from_hf_repo" says "repo": it reads repositories.
    • private-dataThe description's first sentence says "read" and "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_gpusThe GPUs and machines nodegrove.io covers: memory, the memory a runtime can use and bandwidth, from the makers' specs, with each one's page.No findings

    Why it is in this group

    • The name "list_gpus" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.nodegrove.io/mcp: tools/list returned 6 tools to an anonymous client, including can_i_run (write), what_fits (write), estimate_vram (write), list_models (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "can_i_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "can_i_run" says "run": a word for a change.

    What this check looks for
  • The server marks "what_fits" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.

    What this check looks for
  • The server marks "list_models" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_models" says "list": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.1.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http vram https://mcp.nodegrove.io/mcp
claude mcp add --transport http vram https://mcp.nodegrove.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__vram__estimate_from_hf_repo",
      "mcp__vram__list_gpus"
    ],
    "ask": [
      "mcp__vram__can_i_run",
      "mcp__vram__what_fits",
      "mcp__vram__estimate_vram",
      "mcp__vram__list_models"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vram. Review it before you use it.

Capability tags behind 3 rules
  • mcp__vram__can_i_run untrusted-input
  • mcp__vram__estimate_vram untrusted-input
  • mcp__vram__estimate_from_hf_repo private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.nodegrove/vram-mcp/verify?hash=40bd893f7c00cf28059764421c51dcd9a4da6e22a971c1bb0a45187e6f6a8647" | jq -e '.changed == false'

Pinned hash 40bd893f7c00, from Nov 17, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.nodegrove/vram-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.nodegrove/vram-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.nodegrove/vram-mcp.svg)](https://radar.anlyon.com/servers/io.nodegrove/vram-mcp)

Source: MCP Registry · repository. Synced Nov 3, 2026, 21:18 UTC.

Nodegrove VRAM: can I run it? MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Nodegrove VRAM: can I run it? MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Nodegrove VRAM: can I run it? MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Nodegrove VRAM: can I run it? MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Nodegrove VRAM: can I run it? MCP server have?

6 tools: 4 write, 2 read. can_i_run, what_fits, estimate_vram, list_models, estimate_from_hf_repo and list_gpus.

Does the Nodegrove VRAM: can I run it? MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Nodegrove VRAM: can I run it? MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Nodegrove VRAM: can I run it? MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.