GPU Cloud
REMOTE · GPUCLOUD.CA
Rent H100, RTX PRO 6000, A100, L40 and RTX A6000 GPUs by the hour in Montréal, Canada, in CAD.
Available components
Last scanned (16 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Cloud Infrastructure
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (gpucloud_delete_server). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 8506 tokens (~137/item across 62 items; 62 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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 63 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Oct 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- New tool “gpucloud_list_contracts” functional
- New tool “gpucloud_list_monthly_rentals” functional
- 11 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “gpucloud_create_server” rewrote its description, which is the text the model reads security
- Tool “gpucloud_get_auto_reload” rewrote its description, which is the text the model reads security
- Tool “gpucloud_hibernate_server” rewrote its description, which is the text the model reads security
- Tool “gpucloud_list_images” rewrote its description, which is the text the model reads security
- Tool “gpucloud_list_templates” rewrote its description, which is the text the model reads security
- Tool “gpucloud_quote_server” rewrote its description, which is the text the model reads security
- Tool “gpucloud_set_auto_reload” rewrote its description, which is the text the model reads security
- Tool “gpucloud_start_server” rewrote its description, which is the text the model reads security
- Schema quality: 113 → 136 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “gpucloud_cancel_reservation” functional
- New tool “gpucloud_list_reservations” functional
- New tool “gpucloud_reserve_server” functional
- New tool “gpucloud_set_server_threshold_action” functional
- “gpucloud_create_server” added an optional parameter “onFundsExhausted” cosmetic
- “gpucloud_quote_server” added an optional parameter “onFundsExhausted” cosmetic
- “gpucloud_set_auto_reload” added an optional parameter “monthlyCapCad” cosmetic
- 10 Oct 26 65
First indexed and scored.
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 18 Oct 2026 · Probed https://gpucloud.ca/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gpucloud.ca | CN=YE1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6badec68aa5a0121731915e5d01571709cd |
| SANs: *.gpucloud.ca, gpucloud.ca | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gpucloud.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| gpucloud.ca. | 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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://code.jquery.com https://*.tib.finance https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://*.tib.finance; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; frame-src https://*.tib.finance; connect-src 'self' https://*.tib.finance https://www.google-analytics.com https://region1.google-analytics.com https://www.googletagmanager.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gpucloud.ca/api/mcp | Verified | 200 | |
| http (plaintext) | http://gpucloud.ca/api/mcp | HTTPS enforced | 301 | https://gpucloud.ca/api/mcp |
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 →
gpucloud_restore_server Restore a hibernated server (spends money) ~114
Restores a hibernated server (billed like a start: hourly billing resumes; takes a few minutes and depends on GPU availability). A NEW public IP address is assigned: poll gpucloud_get_server until publicIpv4 is set (publicIpStatus / publicIpNote explain the wait) and never reuse the previous address. [SPENDS MONEY] (permission: servers:start) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| serverId | string | yes | Server id (from gpucloud_list_servers). |
No output schema declared.
No examples provided.
gpucloud_restore_server_backup Restore a backup to a new server (spends money) ~193
Creates a NEW server (same GPU model and region) from an AVAILABLE backup; the original server is not changed. Billed like a new hourly server: the first hour from credits now, then per hour. Needs canLaunch, a saved card, credits for one hour, the budget and key caps. Two steps: without confirmationToken returns the price and a token; with it, launches. Poll gpucloud_get_server for the new server. [SPENDS MONEY] (permission: servers:create) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| backupId | string | yes | Backup id (from gpucloud_list_server_backups). |
| confirmationToken | string | – | Token returned by the previous call without token, valid 10 minutes, single use. |
| name | string | – | Display name of the new server. |
| serverId | string | yes | Server id (from gpucloud_list_servers). |
No output schema declared.
No examples provided.
gpucloud_set_auto_reload Change auto-reload ~253
Turns automatic credit reload on/off. Needs canCharge; the reload amount may not exceed the key max single charge, and every reload counts in this key monthly card-charge cap and in the account budget limit. Turning it on (or changing it while on) takes two steps: without confirmationToken returns the settings and a token; call again with the same arguments and the token once the user approved. Turning it off applies at once. Threshold $10-$5,000, amount $25-$10,000. monthlyCapCad: the most the automatic reloads may charge per calendar month (Montreal time), $25-$100,000, null = no cap, absent = unchanged (200 for a new configuration); once reached, no automatic reload until next month and the user is told. It never limits a manual payment. [SPENDS MONEY] (permission: billing:auto_reload) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Token returned by the previous call (valid 10 minutes, single use). |
| enabled | boolean | yes | – |
| monthlyCapCad | – | – | – |
| reloadAmountCad | number | yes | – |
| thresholdCad | number | yes | – |
No output schema declared.
No examples provided.
gpucloud_set_budget Set the account budget limit ~201
Sets the monthly budget limit of the account. Lowering the limit (or setting one where there was none) applies at once. Raising or removing it needs the owner's approval: without confirmationToken it returns the change and a token; call again with the same arguments and the token once the user approved. Raising the limit does not restore hibernated servers. (permission: billing:budget) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| alertPercent | integer | – | Alert e-mail threshold, percent of the limit (default 80). |
| confirmationToken | string | – | Token returned by the previous call (valid 10 minutes, single use). Only needed to raise or remove the limit. |
| dailyLimitCad | – | – | Optional DAILY budget limit in CAD (calendar day America/Toronto), null to remove it, omitted to keep it. |
| monthlyLimitCad | – | yes | New monthly budget limit in CAD, or null to remove the limit. |
No output schema declared.
No examples provided.
gpucloud_set_notices Turn GPU Cloud notices on or off ~127
A tool result may end with a short "GPU Cloud notice for the user" (payment card to update, top-up offer when the balance runs low, GPU available now). Payment and balance notices come at most once an hour; GPU offers come with the catalog and price results, and at most every 2 hours elsewhere. Turn them off (enabled: false) or back on (enabled: true) for THIS MCP key only. Changes nothing else. (permission: account:notices) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
No output schema declared.
No examples provided.
gpucloud_set_server_backup_policy Backup option of a server ~210
Turns the backup option of a server on or off, or changes its hour (hourLocal 0-23, Eastern time) and retention (1-7 daily backups). Turning it ON costs 9.99 $/month (hourly servers: pro rata per billed hour; prepaid: the rest of the paid period now from credits, then with each renewal). Turning it OFF deletes the server's backups (needs canDelete when backups exist; no refund of the current period). On/off take two steps (confirmationToken); hour / retention changes apply directly. [SPENDS MONEY] (permission: servers:backup) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Token returned by the previous call without token, valid 10 minutes, single use. |
| enabled | boolean | – | – |
| hourLocal | integer | – | – |
| retention | integer | – | – |
| serverId | string | yes | Server id (from gpucloud_list_servers). |
No output schema declared.
No examples provided.
gpucloud_set_server_threshold_action Set the action at the threshold ~147
What happens to an hourly server when the account balance reaches its threshold and no automatic reload brings it back: HIBERNATE (kept 12 h with an hourly hibernation fee, restarted as soon as the balance is back, then deleted) or DELETE (deleted at once, no hibernation fee, data lost). Machines that cannot be hibernated (spot) only accept DELETE. Spends nothing. (permission: servers:update) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| onFundsExhausted | string | yes | HIBERNATE or DELETE. |
| serverId | string | yes | Server id (from gpucloud_list_servers). |
No output schema declared.
No examples provided.
gpucloud_start_server Start a server (spends money) ~103
Starts a stopped server (a stopped hourly server is already billed; the next hour must be covered: credits, or a charge of the saved card within the caps). No card is needed when the credits cover it. For a hibernated server use gpucloud_restore_server. [SPENDS MONEY] (permission: servers:start) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| serverId | string | yes | Server id (from gpucloud_list_servers). |
No output schema declared.
No examples provided.
gpucloud_stop_server Stop a server ~115
Stops (shuts down) a server. Disk and data are kept. WARNING: a stopped server is STILL BILLED at its full hourly rate (the GPU stays reserved). To pay much less, use gpucloud_hibernate_server instead (a hibernated server is billed a small hibernation rate); to stop paying entirely, delete it. (permission: servers:stop) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| serverId | string | yes | Server id (from gpucloud_list_servers). |
No output schema declared.
No examples provided.
gpucloud_topup_credits Buy credits (charges the card) ~110
Buys credits with the saved card, within the key caps (max single charge, monthly charges). Two steps: without confirmationToken returns the amount and a token; with it, charges the card (the owner is emailed). [SPENDS MONEY] (permission: billing:charge) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| amountCad | number | yes | – |
| confirmationToken | string | – | Token returned by the previous call (valid 10 minutes, single use). |
No output schema declared.
No examples provided.
gpucloud_update_profile Update profile ~63
Change the first and last name of the account. Email and password cannot be changed through MCP. (permission: profile:write) [Requires a free GPU Cloud account and MCP key]
| Name | Type | Req | Description |
|---|---|---|---|
| firstName | string | yes | – |
| lastName | string | yes | – |
No output schema declared.
No examples provided.
gpucloud_whoami Who am I ~72
The GPU Cloud account behind this MCP key: user, key permissions and spend caps, budget used/remaining this month, credit balance and whether a payment card is saved (required for any spend). Call this first. (permission: account:read) [Requires a free GPU Cloud account and MCP key]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the GPU Cloud MCP server?
GPU Cloud is a hosted endpoint at https://gpucloud.ca/api/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 · gpucloud.ca
claude mcp add --transport http ca-gpucloud-gpu-cloud 'https://gpucloud.ca/api/mcp'
What is the GPU Cloud MCP server?
GPU Cloud is an MCP server listed in the public MCP registry as ca.gpucloud/gpu-cloud. Rent H100, RTX PRO 6000, A100, L40 and RTX A6000 GPUs by the hour in Montréal, Canada, in CAD. This page covers its hosted endpoint (https://gpucloud.ca/api/mcp).
Is the GPU Cloud MCP server safe to use?
GPU Cloud scores 68 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 Cloud MCP server expose?
GPU Cloud exposes 62 tools: gpucloud_whoami, gpucloud_get_profile, gpucloud_update_profile, gpucloud_list_tickets, gpucloud_create_ticket, and 57 more. Their descriptions and schemas cost roughly 7,789 tokens of context every time the server is loaded.
Does the GPU Cloud MCP server require authentication?
No. We connected to GPU Cloud without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GPU Cloud MCP server still maintained?
GPU Cloud is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.