# io.usefulapi/upcloud (remote · upcloud.usefulapi.io)

Inspect servers, storage, networks, databases and billing, and start, stop or back up servers.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `upcloud.usefulapi.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-upcloud/upcloud.md), [page](https://verifymcp.io/servers/io-usefulapi-upcloud/upcloud)

## Channel facts

- Endpoint: `https://upcloud.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2474 tokens (~112/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/upcloud MCP server?

io.usefulapi/upcloud is a hosted endpoint at https://upcloud.usefulapi.io/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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-upcloud 'https://upcloud.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-upcloud": {
      "url": "https://upcloud.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-upcloud": {
      "type": "http",
      "url": "https://upcloud.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-upcloud]
url = "https://upcloud.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-upcloud": {
      "type": "remote",
      "url": "https://upcloud.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-upcloud --url 'https://upcloud.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-upcloud:
    url: "https://upcloud.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-upcloud": {
      "Transport": "http",
      "Url": "https://upcloud.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-upcloud -t streamable-http -u 'https://upcloud.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-upcloud": {
      "type": "http",
      "url": "https://upcloud.usefulapi.io/mcp"
    }
  }
}
```

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-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 77, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 76, +48)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-30 (score 28, +10)

- [security improvement] Transport: fail → pass

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (22)

### `upcloud_get_account` (~57 tokens)

Get account

The calling account: username, remaining credits and resource limits (cores, memory, storage per tier, IPs, networks, managed services). A cheap way to confirm the token works. UpCloud: GET /1.3/account.

### `upcloud_list_zones` (~68 tokens)

List zones

Available zones (data centres) with id (e.g. fi-hel1, de-fra1, us-chi1), description and whether they are public or private-cloud. Zone ids are used by every other resource. UpCloud: GET /1.3/zone.

### `upcloud_list_plans` (~61 tokens)

List server plans

Fixed-price server plans: name (e.g. 2xCPU-4GB), cores, memory, included storage size/tier and transfer, plus GPU model/amount for GPU plans. UpCloud: GET /1.3/plan.

### `upcloud_list_prices` (~53 tokens)

List prices

The price list per zone in the account's currency: per-hour prices for plans, cores, memory, storage tiers, backups, IPv4 addresses and traffic. UpCloud: GET /1.3/price.

### `upcloud_get_billing_summary` (~117 tokens)

Get monthly billing summary

Billing summary for one month with per-resource details (servers, storages, managed databases, object storage, …: amount, hours, plan, zone, labels) and totals. Needs an account allowed to read billing. UpCloud: GET /1.3/account/billing/summary/{yearmonth}.

Input parameters:

- `resource_id` (string): Only this resource: its UUID, or for IP addresses the address itself.
- `yearmonth` (string, required): The month, YYYY-MM, e.g. 2026-09.

### `upcloud_list_servers` (~226 tokens)

List servers

Cloud servers on the account (summary: uuid, title, hostname, zone, plan, cores, memory, state, tags, labels). Filter by state, a free-text search (name, title, uuid, zone, IP, hostname, tag or template), tags or labels. Use upcloud_get_server for IPs and disks. UpCloud: GET /1.3/server.

Input parameters:

- `label` (array): Label filters: a key (`env`) or key=value (`env=prod`). Several are ANDed. Keys match case-insensitively.
- `limit` (integer): Max servers to return (use with offset to page).
- `offset` (integer): Offset into the results (API default 0).
- `search` (string): Match by name, title, uuid, zone, IP address, hostname, tag name or template name.
- `state` (string): Only servers in this state.
- `tag` (string): Tag filter: `a,b` matches servers with ANY of the tags, `a:b` servers with ALL of them.

### `upcloud_get_server` (~74 tokens)

Get server details

Full details of one server: state, plan, cores/memory, network interfaces and IP addresses, attached storage devices, firewall on/off, simple-backup schedule, labels, tags and remote-access settings. UpCloud: GET /1.3/server/{uuid}.

Input parameters:

- `server_uuid` (string, required): The server UUID.

### `upcloud_list_storages` (~140 tokens)

List storages

Storage devices: disks, backups, CD-ROM images and OS templates (uuid, title, type, tier, size GB, state, zone, labels). Narrow by `kind`: private (yours), public (UpCloud-provided), normal (disks), backup, cdrom, template or favorite. UpCloud: GET /1.3/storage[/{kind}].

Input parameters:

- `kind` (string): Narrow the list. Omit for every accessible storage.
- `label` (array): Label filters: a key (`env`) or key=value (`env=prod`). Several are ANDed. Keys match case-insensitively.

### `upcloud_get_storage` (~81 tokens)

Get storage details

Details of one storage: size, tier, state (e.g. online, backuping), encryption, the servers it is attached to, its backups and backup_rule. Poll this to follow a backup started with upcloud_create_storage_backup. UpCloud: GET /1.3/storage/{uuid}.

Input parameters:

- `storage_uuid` (string, required): The storage UUID.

### `upcloud_list_ip_addresses` (~64 tokens)

List IP addresses

Every IP address on the account: address, family (IPv4/IPv6), access (public/utility/private), the server it is assigned to, zone, PTR record, floating flag and release policy. UpCloud: GET /1.3/ip_address.

### `upcloud_list_firewall_rules` (~86 tokens)

List server firewall rules

The firewall rules of one server in evaluation order (position, direction, action, family, protocol, address and port ranges, comment). Whether the firewall is enabled at all is the `firewall` field of upcloud_get_server. UpCloud: GET /1.3/server/{uuid}/firewall_rule.

Input parameters:

- `server_uuid` (string, required): The server UUID.

### `upcloud_list_networks` (~114 tokens)

List networks

Networks visible to the account — public, utility and private SDN networks — with their IP subnets, DHCP settings, routes, attached servers and peerings. Optionally only one zone. UpCloud: GET /1.3/network/.

Input parameters:

- `label` (array): Label filters: a key (`env`) or key=value (`env=prod`). Several are ANDed. Keys match case-insensitively.
- `zone` (string): Only networks in this zone, e.g. fi-hel1.

### `upcloud_list_databases` (~142 tokens)

List managed databases

Managed Database services (PostgreSQL, MySQL, Valkey, OpenSearch): uuid, title, type, plan, zone, state, component hosts/ports, backups and labels. Note the response can include connection URIs with credentials. UpCloud: GET /1.3/database.

Input parameters:

- `label` (array): Label filters: a key (`env`) or key=value (`env=prod`). Several are ANDed. Keys match case-insensitively.
- `limit` (integer): Max entries to return, 0-100 (API default 10).
- `offset` (integer): Offset into the results (API default 0).

### `upcloud_list_load_balancers` (~123 tokens)

List managed load balancers

Managed Load Balancer services with their frontends, backends and members, networks, plan, zone, configured status and operational state. UpCloud: GET /1.3/load-balancer.

Input parameters:

- `label` (array): Label filters: a key (`env`) or key=value (`env=prod`). Several are ANDed. Keys match case-insensitively.
- `limit` (integer): Max entries to return, 0-100 (API default 10).
- `offset` (integer): Offset into the results (API default 0).

### `upcloud_list_kubernetes_clusters` (~58 tokens)

List Kubernetes clusters

Managed Kubernetes clusters: name, uuid, zone, plan, state, network/CIDR, control-plane IP filter, labels and node groups (plan, count, state). UpCloud: GET /1.3/kubernetes.

### `upcloud_list_object_storages` (~115 tokens)

List managed object storages

Managed Object Storage (S3-compatible) services: uuid, name, region, configured status and operational state, public/private endpoints, custom domains and labels. UpCloud: GET /1.3/object-storage-2.

Input parameters:

- `limit` (integer): Max entries to return, 0-100 (API default 10).
- `offset` (integer): Offset into the results (API default 0).
- `sort` (string): Order of results; prefix - for descending (API default -created_at).

### `upcloud_list_audit_logs` (~225 tokens)

List audit logs

Security audit trail of the account (up to 180 days): who did what to which resource, when, from which IP and via API or Hub. Filter by action, origin, resource type, time window or a keyword (UUID, username or IP). Returns total_count for paging. UpCloud: GET /1.3/audit-logs.

Input parameters:

- `action` (string): Only this action.
- `created_after` (string): ISO timestamp, e.g. 2026-09-01T00:00:00Z (inclusive). Default 180 days ago.
- `created_before` (string): ISO timestamp (inclusive). Default now.
- `limit` (integer): Max entries to return, 0-200 (API default 50).
- `offset` (integer): Offset into the results (API default 0).
- `origin` (string): Only this origin.
- `q` (string): Keyword: a resource UUID, account username or IP address.
- `resource_type` (string): Only this resource type (uks = Kubernetes).

### `upcloud_start_server` (~95 tokens)

Start a server

Start a stopped server (billing for a started server resumes). Fails with 409 if it is not stopped. `async` returns immediately — poll upcloud_get_server for state=started. UpCloud: POST /1.3/server/{uuid}/start.

Input parameters:

- `server_uuid` (string, required): The server UUID.
- `start_type` (string): sync (default) waits for the start; async returns at once.

### `upcloud_stop_server` (~137 tokens)

Stop a server

DISRUPTIVE: stop a running server — it goes offline until started again with upcloud_start_server. soft (default) sends an ACPI shutdown; with a timeout, a hard stop follows if it is still running. hard is like pulling the plug and can lose unsaved data. UpCloud: POST /1.3/server/{uuid}/stop.

Input parameters:

- `server_uuid` (string, required): The server UUID.
- `stop_type` (string): soft = ACPI shutdown signal (default); hard = equivalent of pulling the power cable.
- `timeout` (integer): Soft-stop timeout in seconds, 1-600.

### `upcloud_restart_server` (~168 tokens)

Restart a server

DISRUPTIVE: stop and start a running server. soft (default) needs a timeout: after it, timeout_action=destroy hard-stops and restarts, ignore (API default) aborts and leaves the server running. hard power-cycles immediately. UpCloud: POST /1.3/server/{uuid}/restart.

Input parameters:

- `server_uuid` (string, required): The server UUID.
- `stop_type` (string): soft = ACPI shutdown signal (default); hard = equivalent of pulling the power cable.
- `timeout` (integer): Soft-stop timeout in seconds, 1-600. Required for a soft restart.
- `timeout_action` (string): What to do if the soft stop times out: destroy (hard stop, then start) or ignore (give up).

### `upcloud_create_storage_backup` (~107 tokens)

Back up a storage

Take an on-demand, point-in-time backup of a storage device. Additive (nothing is overwritten) but backups are billed per GB. Asynchronous: the storage goes to a backuping/maintenance state and back to online — poll upcloud_get_storage. UpCloud: POST /1.3/storage/{uuid}/backup.

Input parameters:

- `storage_uuid` (string, required): The storage UUID.
- `title` (string, required): A short description for the backup, 1-255 characters.

### `upcloud_modify_server` (~163 tokens)

Rename a server / set its backup schedule

Change a server's title, hostname and/or simple-backup schedule. Only these reversible fields are exposed — no resizing or plan change (billing) and no firewall toggle. simple_backup is `HHMM,daily|dailies|weeklies|monthlies` (UTC time) or `no` to disable. UpCloud: PUT /1.3/server/{uuid}.

Input parameters:

- `hostname` (string): A valid hostname, e.g. web1.example.com (max 128).
- `server_uuid` (string, required): The server UUID.
- `simple_backup` (string): e.g. 0430,dailies — or `no` to turn simple backups off.
- `title` (string): A short informational description, 0-255 characters.

## Diagnostics

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

## Score history

- 2026-10-04: 78
- 2026-10-03: 77
- 2026-10-02: 77
- 2026-10-01: 76
- 2026-09-30: 28
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/upcloud MCP server?

io.usefulapi/upcloud is an MCP server listed in the public MCP registry as io.usefulapi/upcloud. Inspect servers, storage, networks, databases and billing, and start, stop or back up servers. This page covers its hosted endpoint (https://upcloud.usefulapi.io/mcp).

### Is the io.usefulapi/upcloud MCP server safe to use?

io.usefulapi/upcloud scores 78 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.usefulapi/upcloud MCP server expose?

io.usefulapi/upcloud exposes 22 tools: upcloud_get_account, upcloud_list_zones, upcloud_list_plans, upcloud_list_prices, upcloud_get_billing_summary, and 17 more. Their descriptions and schemas cost roughly 2,474 tokens of context every time the server is loaded.

### Does the io.usefulapi/upcloud MCP server require authentication?

Yes. io.usefulapi/upcloud asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.usefulapi/upcloud MCP server still maintained?

io.usefulapi/upcloud is still listed as active in the MCP registry. We last reached this channel on 4 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://upcloud.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-upcloud/upcloud.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-upcloud/upcloud.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-upcloud/upcloud