Remote MCP · Endpoint

Nodegrove VRAM: can I run it? MCP server

No. Nodegrove VRAM: can I run it? answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.nodegrove.io/mcp

The last check completed an MCP handshake.

Registry name
io.nodegrove/vram-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU.
Listing
From the official MCP registry (active).
Recent checks of Nodegrove VRAM: can I run it?
CheckedResultHandshake
43 minutes agoHandshake completed151 ms
3 days agoHandshake completed149 ms
13 days agoHandshake completed180 ms
13 days agoHandshake completed196 ms
15 days agoHandshake completed200 ms
15 days agoHandshake completed153 ms
17 days agoHandshake completed152 ms
18 days agoHandshake completed161 ms
18 days agoHandshake completed63 ms
20 days agoHandshake completed254 ms
22 days agoHandshake completed247 ms
25 days agoHandshake completed227 ms
27 days agoHandshake completed192 ms
29 days agoHandshake completed170 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 23.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Nodegrove VRAM: can I run it? and makes no claim about it beyond what these checks measured.