io.github.jyswee/computegpu
REMOTE · MCP.COMPUTEGPU.COM · 3 COMPONENTS
Rent cloud GPUs from your agent: live catalogue, deploy, stop, destroy. Per-second billing.
Available components
Last scanned (6 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Cloud Infrastructure
Recent critical change
Authorization (17 Oct 2026). See the changelog before you install this server.
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 Security57
- 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 (computegpu_signup). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 149 tokens (~74/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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.
- 23 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.
- 21 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.
- 19 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.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 +31
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- 16 Oct 26 27
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 23 Oct 2026 · Probed https://mcp.computegpu.com/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=computegpu.com | CN=YR1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | RSA 4096 | SHA256-RSA | 5a63278ce064bc77aca6f2eea273c8f5a73 |
| SANs: *.computegpu.com, computegpu.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 mcp.computegpu.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| computegpu.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.computegpu.com/sse | Verified | 200 | |
| http (plaintext) | http://mcp.computegpu.com/sse | HTTPS enforced | 301 | https://mcp.computegpu.com/sse |
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 →
computegpu_get_started ~33
Explains what ComputeGpu is and how to activate this MCP server (no API key on this session yet).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
computegpu_signup ~116
Create a ComputeGpu account. Requires the human's email. Returns an API key (shown once) and unlocks all ComputeGpu tools in this session. Before the first deploy the owner verifies a card ($0, no charge). Ask the human for their email before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The human owner's email. The account and receipts are tied to it. | |
| tenant | string | yes | Short lowercase slug, e.g. "my-agent" (3-64 chars, a-z 0-9 -) |
No output schema declared.
No examples provided.
How do I install the io.github.jyswee/computegpu MCP server?
io.github.jyswee/computegpu is a hosted endpoint at https://mcp.computegpu.com/sse, 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 · mcp.computegpu.com
claude mcp add --transport http jyswee-computegpu 'https://mcp.computegpu.com/sse'
What is the io.github.jyswee/computegpu MCP server?
io.github.jyswee/computegpu is an MCP server listed in the public MCP registry as io.github.jyswee/computegpu. Rent cloud GPUs from your agent: live catalogue, deploy, stop, destroy. Per-second billing. This page covers its hosted endpoint (https://mcp.computegpu.com/sse).
Is the io.github.jyswee/computegpu MCP server safe to use?
io.github.jyswee/computegpu scores 61 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 io.github.jyswee/computegpu MCP server expose?
io.github.jyswee/computegpu exposes 2 tools: computegpu_get_started, computegpu_signup. Their descriptions and schemas cost roughly 149 tokens of context every time the server is loaded.
Does the io.github.jyswee/computegpu MCP server require authentication?
No. We connected to io.github.jyswee/computegpu without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jyswee/computegpu MCP server still maintained?
io.github.jyswee/computegpu is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.