io.usefulapi/upcloud
REMOTE · UPCLOUD.USEFULAPI.IO · SCANNED OCT 4
Inspect servers, storage, networks, databases and billing, and start, stop or back up servers.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · upcloud.usefulapi.io
claude mcp add --transport http io-usefulapi-upcloud 'https://upcloud.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-upcloud": {
"url": "https://upcloud.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-upcloud": {
"type": "http",
"url": "https://upcloud.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-upcloud] url = "https://upcloud.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-upcloud": {
"type": "remote",
"url": "https://upcloud.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-upcloud --url 'https://upcloud.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-upcloud:
url: "https://upcloud.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-upcloud": {
"Transport": "http",
"Url": "https://upcloud.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-upcloud -t streamable-http -u 'https://upcloud.usefulapi.io/mcp'
{
"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.
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.
- 4 Oct 26 +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.
- 2 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +48
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 30 Sept 26 +10
- Transport: fail → pass ▲ security
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://upcloud.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of upcloud.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://upcloud.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://upcloud.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://upcloud.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://upcloud.usefulapi.io/mcp |
| Authorisation server | https://upcloud.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://upcloud.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://upcloud.usefulapi.io/mcp | HTTPS enforced | 301 | https://upcloud.usefulapi.io/mcp |
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 →
upcloud_create_storage_backup Back up a storage ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| storage_uuid | string | yes | The storage UUID. |
| title | string | yes | A short description for the backup, 1-255 characters. |
No output schema declared.
No examples provided.
upcloud_get_account Get account ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upcloud_get_billing_summary Get monthly billing summary ~117
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_id | string | – | Only this resource: its UUID, or for IP addresses the address itself. |
| yearmonth | string | yes | The month, YYYY-MM, e.g. 2026-09. |
No output schema declared.
No examples provided.
upcloud_get_server Get server details ~74
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| server_uuid | string | yes | The server UUID. |
No output schema declared.
No examples provided.
upcloud_get_storage Get storage details ~81
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| storage_uuid | string | yes | The storage UUID. |
No output schema declared.
No examples provided.
upcloud_list_audit_logs List audit logs ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
upcloud_list_databases List managed databases ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
upcloud_list_firewall_rules List server firewall rules ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server_uuid | string | yes | The server UUID. |
No output schema declared.
No examples provided.
upcloud_list_ip_addresses List IP addresses ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upcloud_list_kubernetes_clusters List Kubernetes clusters ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upcloud_list_load_balancers List managed load balancers ~123
Managed Load Balancer services with their frontends, backends and members, networks, plan, zone, configured status and operational state. UpCloud: GET /1.3/load-balancer.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
upcloud_list_networks List networks ~114
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
upcloud_list_object_storages List managed object storages ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
upcloud_list_plans List server plans ~61
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upcloud_list_prices List prices ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upcloud_list_servers List servers ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
upcloud_list_storages List storages ~140
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}].
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
upcloud_list_zones List zones ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upcloud_modify_server Rename a server / set its backup schedule ~163
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | – | A valid hostname, e.g. web1.example.com (max 128). |
| server_uuid | string | yes | 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. |
No output schema declared.
No examples provided.
upcloud_restart_server Restart a server ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server_uuid | string | yes | 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). |
No output schema declared.
No examples provided.
upcloud_start_server Start a server ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server_uuid | string | yes | The server UUID. |
| start_type | string | – | sync (default) waits for the start; async returns at once. |
No output schema declared.
No examples provided.
upcloud_stop_server Stop a server ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server_uuid | string | yes | 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. |
No output schema declared.
No examples provided.
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.