Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

gpu.nz GPU cloud

REMOTE · GPU.NZ · 2 COMPONENTS

Rent cloud GPUs from AI agents: live prices, VRAM estimates, launch, logs and stop.

+3 this week 74 Trust /100

Last scanned (17 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1691 tokens (~105/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 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.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 4 Nov 2026 · Probed https://gpu.nz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gpu.nz CN=YR2,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 RSA 2048 SHA256-RSA 6ca2aff2cb6136587e622159482a6772539
SANs: gpu.nz, www.gpu.nz
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gpu.nz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
nz. present 38240, 62081 8, 8 Verified
gpu.nz. 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
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gpu.nz/mcp Verified 200
http (plaintext) http://gpu.nz/mcp HTTPS enforced 301 https://gpu.nz/mcp
MCP tools · 16 exposed · ~1,505 tokens

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 →

Tool Tokens
add_ssh_key ~72

Adds an SSH public key (a line from a .pub file) to the account. Needs user:write.

NameTypeReqDescription
namestring–A name for the key
public_keystringyesThe public key line, e.g. ssh-ed25519 AAAA… you@laptop

No output schema declared.

No examples provided.

create_instance ~230

Rents the server of an offer and starts it with a template. Billing starts right away and runs every minute until you stop or destroy it. Confirm the price with the user first. Needs instances:write. The response has the instance id; poll get_instance until status is running (usually 1–5 minutes).

NameTypeReqDescription
disk_gbintegeryesDisk size, GB (use the template's recommended_disk_gb)
idempotency_keystring–Reuse the same value when retrying the same request, so a retry never rents twice
imagestring–Docker image, only with the custom template
namestring–A name for the server
offer_idstringyesOffer id from search_offers
ssh_key_idsarray–SSH key ids to install (default: all of yours)
templatestringyesTemplate slug from list_templates, e.g. "comfyui", "ollama", "pytorch", "custom"
typestring–on_demand (default) or interruptible

No output schema declared.

No examples provided.

destroy_instance ~48

Destroys a server and deletes its disk for good; billing stops completely. Irreversible: confirm with the user. Needs instances:write.

NameTypeReqDescription
instance_idstringyesInstance id

No output schema declared.

No examples provided.

estimate_vram ~211

How much GPU memory an AI model needs (LLMs such as Qwen, DeepSeek, Llama, Gemma, GPT-OSS; image and video models such as FLUX, SDXL, Wan) at a given precision and context length, and which GPUs on gpu.nz fit it with their current price. Call without `model` to list the known models.

NameTypeReqDescription
concurrent_requestsinteger–Parallel sequences sharing the GPU (default 1)
context_tokensinteger–LLM context length in tokens (default 8192)
modelstring–Model name or id, e.g. "qwen3-32b", "Llama 3.3 70B", "flux.1-dev"
precisionstring–Weights precision: "fp16", "fp8", "q8", "q6", "q5", "q4" (LLMs; default q4 for LLMs, fp16 for image models)

No output schema declared.

No examples provided.

get_account ~33

The signed-in account and its balance, hourly burn and runway. Needs a key with user:read and billing:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_instance ~78

Status, SSH command, app URLs (ComfyUI, Jupyter, chat…), price and cost so far of one server. The root password is left out unless include_password is true (your SSH keys are installed on every server).

NameTypeReqDescription
include_passwordboolean–Include the root SSH password
instance_idstringyesInstance id

No output schema declared.

No examples provided.

get_instance_logs ~58

The last lines of a server's container log: boot progress, app start-up, errors. Needs instances:read.

NameTypeReqDescription
instance_idstringyesInstance id
tailinteger–How many last lines (default 200)

No output schema declared.

No examples provided.

get_offer ~34

Details and the current price of one offer by id (from search_offers).

NameTypeReqDescription
offer_idstringyesOffer id

No output schema declared.

No examples provided.

list_gpu_models ~86

GPU models available on gpu.nz right now with VRAM, class and the cheapest hourly price per GPU. Use it to pick a gpu_slug for search_offers.

NameTypeReqDescription
min_vram_gbnumber–Only models with at least this much VRAM per GPU
querystring–Filter by name, e.g. "4090" or "H100"

No output schema declared.

No examples provided.

list_instances ~48

Your rented servers with status, GPU, price and SSH command. Needs instances:read.

NameTypeReqDescription
statusstring–active (default): servers that are not destroyed; all: include destroyed ones

No output schema declared.

No examples provided.

list_ssh_keys ~29

SSH public keys on the account; they are installed on new servers. Needs user:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_templates ~81

Ready environments a server can start with: ComfyUI, Stable Diffusion Forge, Ollama + Open WebUI, vLLM, Jupyter/PyTorch, Kohya, FluxGym, Unsloth, chats with preloaded models, plain Ubuntu + CUDA, or a custom Docker image. Pass `slug` as `template` to create_instance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_offers ~310

Search rentable GPU servers (offers) with live prices. Returns the cheapest matches first unless `order` says otherwise. Each result has an offer id for create_instance.

NameTypeReqDescription
countrystring–ISO-2 country codes, comma-separated, e.g. "DE,NL,FI"
gpustring–GPU model slug(s), comma-separated, e.g. "rtx-4090-24gb" or "h100-sxm-80gb,h100-pcie-80gb" (see list_gpu_models)
limitinteger–How many offers to return (default 10)
max_price_rub_hnumber–Maximum price for the whole server, rubles per hour
min_disk_gbnumber–Minimum disk the server can give, GB
min_reliabilitynumber–Minimum host reliability, 0–1 (0.98 is a good bar)
min_vram_gbnumber–Minimum VRAM per GPU, GB
num_gpusstring–GPUs per server, comma-separated, e.g. "1" or "2,4,8"
orderstring–Sort: price (default), dlperf_per_price for value, reliability, vram, inet_down
typestring–on_demand (default) or interruptible (cheaper, can be preempted)
verifiedboolean–Only verified datacenters

No output schema declared.

No examples provided.

start_instance ~38

Starts a stopped server again; GPU billing resumes. Confirm with the user. Needs instances:write.

NameTypeReqDescription
instance_idstringyesInstance id

No output schema declared.

No examples provided.

stop_instance ~73

Stops a running server: the GPU is released and billing drops to the disk only. Data on the disk is kept and the server can be started again (the GPU may then be taken by someone else; gpu.nz finds a replacement when it is). Needs instances:write.

NameTypeReqDescription
instance_idstringyesInstance id

No output schema declared.

No examples provided.

topup_link ~76

A link to the balance top-up page (SBP, crypto) for the user to open in a browser; payments never happen through the API. Optionally pre-fills the amount.

NameTypeReqDescription
amountinteger–Amount in the account currency (rubles by default)
languagestring–Page language (default ru)

No output schema declared.

No examples provided.

Install

How do I install the gpu.nz GPU cloud MCP server?

gpu.nz GPU cloud is a hosted endpoint at https://gpu.nz/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 · gpu.nz

# add to Claude Code
claude mcp add --transport http nz-gpu-gpu-cloud 'https://gpu.nz/mcp'
Common questions

What is the gpu.nz GPU cloud MCP server?

gpu.nz GPU cloud is an MCP server listed in the public MCP registry as nz.gpu/gpu-cloud. Rent cloud GPUs from AI agents: live prices, VRAM estimates, launch, logs and stop. This page covers its hosted endpoint (https://gpu.nz/mcp).

Is the gpu.nz GPU cloud MCP server safe to use?

gpu.nz GPU cloud 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 gpu.nz GPU cloud MCP server expose?

gpu.nz GPU cloud exposes 16 tools: list_gpu_models, search_offers, get_offer, list_templates, estimate_vram, and 11 more. Their descriptions and schemas cost roughly 1,505 tokens of context every time the server is loaded.

Does the gpu.nz GPU cloud MCP server require authentication?

No. We connected to gpu.nz GPU cloud without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the gpu.nz GPU cloud MCP server still maintained?

gpu.nz GPU cloud is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.