Developer · Remote MCP server

Nodegrove VRAM: can I run it?

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

Visit Nodegrove VRAM: can I run it?'s website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.nodegrove/vram-mcp
Version
1.0.0
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-10-03
Updated
2026-10-03
Publisher
io.nodegrove
Namespace
Namespace verified by the MCP Registry via the domain nodegrove.io · how
Website
nodegrove.io/mcp
Repository
github.com/nodegrove/vram-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.nodegrove.io/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
nodegrove-vram 1.0.0 · protocol 2025-06-18
Tools discovered
6: can_i_run, what_fits, estimate_vram, estimate_from_hf_repo, list_models, list_gpus
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npmruntime: npx@nodegrove/vram-mcp1.0.0stdioNone declared

How to connect Nodegrove VRAM: can I run it?

Nodegrove VRAM: can I run it? is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.nodegrove.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @nodegrove/vram-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @nodegrove/vram-mcp@1.0.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

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

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
No-Shell Agent Architect MCPTurns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.Remote · HTTPLive check: ✓ handshakeai-automation-operating-pack.vercel.app
Nockchain MCPMoved to io.github.winter0x/nockchain-mcp. This entry is no longer updated.Local · stdionpm: nockchain-mcp
Node RuntimeThis package is intended for demonstration only. Maintained by JFrog Security.Local · stdionpm: @mcp-protocol/node-runtime
NodecelVibe deployment for nodecel - deploy, roll back, diagnose, and manage apps and domains from chat.Remote · HTTPLive check: sign-in requiredmcp.nodecel.com
nodriver - undetected browser automationUndetected anti-bot Chrome automation. 70 tools, parallel isolated browsers.Local · stdioPyPI: nodriver-mcp
NofaxHuman-in-the-loop approvals and notifications for AI coding agents through a local stdio MCP server.Local · stdionpm: nofax
noisefloor - is this number real?Is this number real, or is it noise? Peek-safe A/B tests, change detection, honest forecasts.Local · stdioPyPI: noisefloor
Noisy CodingVoice interface for Claude Code: talk to your agent and it talks back while it works.Local · HTTPOCI image (Docker): docker.io/noisy/noisy-coding:2.13.3