GPU Cloud MCP: what works in Claude, ChatGPT, Cursor, and Grok Bot
Rent H100, RTX PRO 6000, A100, L40 and RTX A6000 GPUs by the hour in Montréal, Canada, in CAD.
Registry name: ca.gpucloud/gpu-cloud (v1.0.0)
Status grid
| App | Status | Date tested |
|---|---|---|
| Claude | Untested | Not yet tested |
| ChatGPT | Untested | Not yet tested |
| Cursor | Untested | Not yet tested |
| Grok Bot | Untested | Not yet tested |
| MCP Inspector (reference client) | Untested | Not yet tested |
| MCP TypeScript SDK (reference client) | Untested | Not yet tested |
Hands-on test results
No hands-on tests yet. We do not publish results until we have actually tested.
Automated handshake
No public remote endpoint to check (local or package-only server).
Gotchas
None recorded yet. Gotchas come only from hands-on tests.
Compare with other tested connectors | Connector Weather
Request a hands-on test of GPU Cloud
Get the badge
Maintain GPU Cloud or write about it? Show its live ConnectorReport status in your README or docs.
Markdown (README, docs)
[](https://connectorreport.com/c/ca-gpucloud-gpu-cloud?utm_source=badge&utm_medium=embed&utm_campaign=ca-gpucloud-gpu-cloud)
HTML
<a href="https://connectorreport.com/c/ca-gpucloud-gpu-cloud?utm_source=badge&utm_medium=embed&utm_campaign=ca-gpucloud-gpu-cloud"><img src="https://connectorreport.com/badge/ca-gpucloud-gpu-cloud.svg" alt="GPU Cloud MCP status on ConnectorReport"/></a>
The badge updates on its own after every retest. How badges work