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.

CloudGPU MCP

NPM · CLOUDGPU-MCP · 2 COMPONENTS

Agent GPU compute scheduling: compare billing, approve budgets, run tasks and persist results.

−6 this week 69 Trust /100

Last scanned (10 hours ago)

Scores higher than 40% of npm servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security48
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to cloudgpu-app/cloudgpu-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 5957 tokens (~97/item across 61 items; 60 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 62 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +11
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
    • Dependency health: unverified → 0.83 ▲ functional
    • Package version: 0.16.7 → 0.16.8 functional
  • 20 Nov 26 −25
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.83 → unverified ▼ functional
    • Package version: 0.16.6 → 0.16.7 functional
  • 19 Nov 26 +1

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

  • 18 Nov 26 +26
    • CVE-2023-54404 no longer affects this package ▲ security
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
  • 17 Nov 26 −20
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.84 → unverified ▼ functional
    • Package version: 0.16.3 → 0.16.6 functional
    • Package version: 0.16.3 → 0.16.5 functional
  • 15 Nov 26 +1

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

  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: fail → unverified ▼ security
    • Stability: 0.00 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Schema quality: 4217 → 5394 ▼ functional
    • Schema quality: 4217 → 5061 ▼ functional
    • Schema quality: 4217 → 5052 ▼ functional
    • Dependency health: 0.84 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 0.13.1 → 0.16.3 functional
    • Package version: 0.13.1 → 0.16.2 functional
    • Package version: 0.13.1 → 0.16.1 functional
    • Package version: 0.13.1 → 0.15.0 functional
    • Package version: 0.13.1 → 0.14.1 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 21 Nov 2026 · Analysed npm/cloudgpu-mcp@0.16.8

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo cloudgpu-app/cloudgpu-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/cloudgpu-app/cloudgpu-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 4033342964
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ab255f71469946c4cc2bc2a3f7c13335931340342dad9b136d5bda0eb70851a4a1627d26151feb9f3fcddf4e093b4bda5c9a31a11964a34aff8e98984

Background: How many MCP packages publish verified provenance →

Dependencies 99 packages
Packages resolved 99
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 60 exposed · ~5,127 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
run_job ~556

Costs money. CloudGPU starts a GPU, runs one bash command on it, then destroys the GPU, all on its servers, so it finishes even if this assistant disconnects. max_spend_usd and max_hours are enforced by the servers. Retrying with the same idempotency_key never starts a second GPU; this tool generates one if you leave it out and returns it. The disk is erased when the job ends. When automatic_output_collection is available, declare outputs and write only those files under $CLOUDGPU_OUTPUT_DIR for persistent storage before release. Otherwise upload results yourself or print them. Storage retention and fees follow the account policy; collection consumes the same GPU budget and may fail. Requires the user's explicit yes on the GPU, budget and time limit.

NameTypeReqDescription
billing_acceptedboolean–true only after the user accepts the quoted minimum and billing period; budget must cover that minimum
billing_quote_idstring–Accepted source-specific billing quote from estimate_cost; expires after five minutes. Required for whole-hour sources.
commandstringyesbash command or script to run on the GPU
disk_gbinteger–Larger system disk: 100, 200 or 500; omit for the standard disk
gpu_countinteger––
gpu_modelstring–GPU model exactly as list_gpus returns it
idempotency_keystring–Reuse the same value when retrying the same job
max_hoursnumberyesHard time limit in hours (at most 24)
max_spend_usdnumberyesBudget for this job in USD (at most 50)
model_referencesarray–Pinned public model references from resolve_model_reference. Downloads into $CLOUDGPU_MODEL_DIR/<name> before the command; download time consumes the same GPU budget. No R2 cache or remote repository…
outputsobject–Explicit relative output files under $CLOUDGPU_OUTPUT_DIR; no globs, symlinks, hidden or credential files. Default total limit 10 MiB, maximum 100 MiB. Only set accept_storage_charges=true after the…
quote_idstring–Server quote from quote_compute, starting quote_; binds configuration and checks price at submission
templatestring–Template id from list_templates
user_confirmedbooleanyestrue only if the user explicitly approved the GPU, budget and time limit
workspace_version_idstring–Immutable Workspace version to restore before the command; requires enabled persistent storage

No output schema declared.

No examples provided.

run_job_batch ~120

Paid: submit an explicitly approved immutable manifest using existing durable Jobs, each with a quote, budget and deadline. Aggregate worst-case budget is capped. Partial success is possible. On lost responses replay the IDENTICAL manifest/key; never create replacement GPUs or retry failed execution automatically. Persist the returned receipt. No transaction rollback or independent batch scheduler.

NameTypeReqDescription
approved_plan_sha256stringyes–
batch_keystringyes–
jobsarrayyes–
total_budget_usdnumberyes–
user_confirmedbooleanyes–

No output schema declared.

No examples provided.

run_server_job_batch ~113

Paid. Use the exact reviewed prepare_job_batch manifest/hash. Enqueue is atomic and persists on the server; each Job reserves its own budget and waits for account/key concurrency. No automatic command retries and no partial client-side fallback. Whole-hour Jobs require a separate accepted current billing quote per allocation.

NameTypeReqDescription
approved_plan_sha256stringyes–
batch_keystringyes–
jobsarrayyes–
total_budget_usdnumberyes–
user_confirmedbooleanyes–

No output schema declared.

No examples provided.

save_job_output ~127

With approval, persist the ended Job log tail as a small Artifact using existing storage quota and retention. This is not the full log or binary output collection. Refuses recognizable credentials, quoted/aliased fields and bounded escaped representations or queried URLs. This is not a guarantee that arbitrary logs contain no secrets; save only logs you know are sanitized. Never touches GPU resources. Reuses a matching verified snapshot when found; cross-client concurrent calls may create duplicates.

NameTypeReqDescription
accept_storage_chargesboolean––
job_idstringyes–
user_confirmedbooleanyes–

No output schema declared.

No examples provided.

save_workspace ~109

Saves 1–100 regular project files as an immutable version. Refuses secrets and symlinks; skips .git, node_modules, __pycache__ and .venv. Save dependency manifests, not the operating system. Pass the returned workspace_version_id to run_job.

NameTypeReqDescription
accept_storage_chargesboolean–Read get_storage pricing and obtain user agreement before enabling paid storage.
local_dirstringyes–
namestringyes–
workspace_idstring––

No output schema declared.

No examples provided.

stop_instance ~68

Destroys the instance and stops billing. Its disk is erased. If commands were run on it in this session and nothing was downloaded, this refuses unless force=true (only after the user confirms the results are not needed).

NameTypeReqDescription
forceboolean––
instance_idstringyes–

No output schema declared.

No examples provided.

tail_logs ~75

Last lines of a background job's log (job_id) or any log file (path), whether the job is still running and its exit code, plus current GPU utilisation and memory.

NameTypeReqDescription
instance_idstringyes–
job_idstring––
linesinteger––
pathstring––

No output schema declared.

No examples provided.

upload ~108

Copies a local file or directory (this computer) to the instance over SFTP. node_modules, .git and __pycache__ are skipped. Credentials files (.ssh, .env, keys) are refused unless allow_sensitive is true and the user asked for it.

NameTypeReqDescription
allow_sensitiveboolean––
instance_idstringyes–
local_pathstringyes–
remote_pathstringyesDestination on the instance, e.g. /root/project or /root/data/

No output schema declared.

No examples provided.

upload_artifact ~85

Uploads a local regular file in resumable-sized parts. Consumes storage quota; retention and pricing depend on the account policy. Credential files are refused.

NameTypeReqDescription
accept_storage_chargesboolean–Read get_storage pricing first. Set true only after the user agrees to paid storage above the included allowance.
local_pathstringyes–
purposestring––

No output schema declared.

No examples provided.

wait_for_funds ~69

Read-only polling of actual account balance and real-top-up signal for up to 60 seconds. No payment, job submission or authorization. If still pending, return to the owner; do not blindly repeat rentals.

NameTypeReqDescription
min_balance_usdnumberyes–
timeoutinteger––

No output schema declared.

No examples provided.

Install

How do I install the CloudGPU MCP server?

CloudGPU MCP runs locally as an npm package, launched with npx -y cloudgpu-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · cloudgpu-mcp

# add to Claude Code
claude mcp add cloudgpu-app-cloudgpu-mcp -- npx -y cloudgpu-mcp
Common questions

What is the CloudGPU MCP server?

CloudGPU MCP is listed in the public MCP registry as io.github.cloudgpu-app/cloudgpu-mcp. Agent GPU compute scheduling: compare billing, approve budgets, run tasks and persist results. This page covers its npm package (cloudgpu-mcp).

Is the CloudGPU MCP server safe to use?

CloudGPU MCP scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 CloudGPU MCP server expose?

CloudGPU MCP exposes 60 tools: request_top_up, wait_for_funds, get_agent_readiness, assess_task_fit, list_rental_regions, and 55 more. Their descriptions and schemas cost roughly 5,127 tokens of context every time the server is loaded.

Is the CloudGPU MCP server still maintained?

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

What licence is the CloudGPU MCP server under?

CloudGPU MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the CloudGPU MCP server?

VerifyMCP ran 15 checks on CloudGPU MCP, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about CloudGPU MCP: Malware scan. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.