# io.github.jyswee/computegpu (remote · mcp.computegpu.com)

Rent cloud GPUs from your agent: live catalogue, deploy, stop, destroy. Per-second billing.

- Trust score: 61/100 (medium)
- Change this week: +34
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

> **Recent critical change**: Authorization (2026-10-17). See the changelog below before you install this server.

## Components

- remote · `mcp.computegpu.com`: 67/100, [markdown](https://verifymcp.io/servers/jyswee-computegpu/mcp.md), [page](https://verifymcp.io/servers/jyswee-computegpu/mcp)
- remote · `mcp.computegpu.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/jyswee-computegpu/mcp-2.md), [page](https://verifymcp.io/servers/jyswee-computegpu/mcp-2)
- npm · `computegpu`: 36/100, [markdown](https://verifymcp.io/servers/jyswee-computegpu/computegpu.md), [page](https://verifymcp.io/servers/jyswee-computegpu/computegpu)

## Channel facts

- Endpoint: `https://mcp.computegpu.com/sse`
- Transports: `sse`
- Auth: `none`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (computegpu_signup).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 149 tokens (~74/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http jyswee-computegpu 'https://mcp.computegpu.com/sse'
```

### Cursor

```json
{
  "mcpServers": {
    "jyswee-computegpu": {
      "url": "https://mcp.computegpu.com/sse"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jyswee-computegpu": {
      "type": "http",
      "url": "https://mcp.computegpu.com/sse"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jyswee-computegpu]
url = "https://mcp.computegpu.com/sse"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jyswee-computegpu": {
      "type": "remote",
      "url": "https://mcp.computegpu.com/sse",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jyswee-computegpu --url 'https://mcp.computegpu.com/sse' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jyswee-computegpu:
    url: "https://mcp.computegpu.com/sse"
```

### Netclaw

```json
{
  "McpServers": {
    "jyswee-computegpu": {
      "Transport": "http",
      "Url": "https://mcp.computegpu.com/sse"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jyswee-computegpu -t streamable-http -u 'https://mcp.computegpu.com/sse'
```

### Other

```json
{
  "mcpServers": {
    "jyswee-computegpu": {
      "type": "http",
      "url": "https://mcp.computegpu.com/sse"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 61, +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.

### 2026-10-21 (score 60, +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.

### 2026-10-19 (score 59, +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.

### 2026-10-18 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-17 (score 58, +31)

- [critical regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-10-16 (score 27)

First indexed and scored.

## MCP tools (2)

### `computegpu_get_started` (~33 tokens)

Explains what ComputeGpu is and how to activate this MCP server (no API key on this session yet).

### `computegpu_signup` (~116 tokens)

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.

Input parameters:

- `email` (string, required): The human owner's email. The account and receipts are tied to it.
- `tenant` (string, required): Short lowercase slug, e.g. "my-agent" (3-64 chars, a-z 0-9 -)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jyswee-computegpu/mcp-2#diagnostics

## Score history

- 2026-10-23: 61
- 2026-10-22: 60
- 2026-10-21: 60
- 2026-10-20: 59
- 2026-10-19: 59
- 2026-10-18: 58
- 2026-10-17: 58
- 2026-10-16: 27

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.computegpu.com/sse
- Repository: https://github.com/jyswee/computegpu-cli
- Website: https://computegpu.com/
- Changelog RSS feed: https://verifymcp.io/servers/jyswee-computegpu/mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/jyswee-computegpu/mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/jyswee-computegpu/mcp-2