MCP servers observed by Lowdown
ca.gpucloud/gpu-cloud MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 63 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ca.gpucloud/gpu-cloud
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ca.gpucloud/gpu-cloud?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
63 tools on 2026-11-16:
gpucloud_add_firewall_rulegpucloud_add_payment_methodgpucloud_add_ssh_keygpucloud_cancel_reservationgpucloud_cancel_servergpucloud_create_ordergpucloud_create_servergpucloud_create_server_backupgpucloud_create_ticketgpucloud_delete_firewall_rulegpucloud_delete_servergpucloud_delete_ssh_keygpucloud_generate_ssh_keygpucloud_get_auto_reloadgpucloud_get_balancegpucloud_get_budgetgpucloud_get_console_urlgpucloud_get_invoicegpucloud_get_ordergpucloud_get_payment_methodgpucloud_get_productgpucloud_get_profilegpucloud_get_servergpucloud_get_server_metricsgpucloud_get_server_usagegpucloud_get_stockgpucloud_hibernate_servergpucloud_list_contractsgpucloud_list_firewall_rulesgpucloud_list_imagesgpucloud_list_invoicesgpucloud_list_monthly_rentalsgpucloud_list_ordersgpucloud_list_productsgpucloud_list_regionsgpucloud_list_reservationsgpucloud_list_server_backupsgpucloud_list_server_snapshotsgpucloud_list_server_volumesgpucloud_list_serversgpucloud_list_ssh_keysgpucloud_list_templatesgpucloud_list_ticketsgpucloud_list_transactionsgpucloud_migrate_servergpucloud_quote_ordergpucloud_quote_servergpucloud_reboot_servergpucloud_renew_servergpucloud_reply_ticketgpucloud_reserve_servergpucloud_restore_servergpucloud_restore_server_backupgpucloud_set_auto_reloadgpucloud_set_budgetgpucloud_set_noticesgpucloud_set_server_backup_policygpucloud_set_server_threshold_actiongpucloud_start_servergpucloud_stop_servergpucloud_topup_creditsgpucloud_update_profilegpucloud_whoami
MCP Registry declaration
- Registry name:
ca.gpucloud/gpu-cloud - Declared version: 1.0.0
- Status: active
- Declared hosts:
gpucloud.ca
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ca.gpucloud/gpu-cloud", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ca.gpucloud/gpu-cloud?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).