Skip to content

UpCloud MCP by usefulapi

io.usefulapi/upcloudusefulapi.iostreamable-httpv1.40.4Scanned

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

22 tools: 5 can delete or cancel things and 17 only read.

Tools: 5 delete, 0 irreversible, 0 write, 17 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the UpCloud MCP by usefulapi can do

The UpCloud MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 22 tools. It can delete or cancel things (5 tools: upcloud_start_server, upcloud_stop_server, upcloud_restart_server, upcloud_create_storage_backup and 1 more). 17 tools only read.

2 tools read private data (upcloud_get_billing_summary and upcloud_list_databases); 1 tool brings in text other people can write (upcloud_list_firewall_rules).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

22 tools

Deletes or cancels 5Claude Code: deny
  • upcloud_create_storage_backupTake an on-demand, point-in-time backup of a storage device.No findings

    Why it is in this group

    • The name "upcloud_create_storage_backup" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Back up a storage
    • destructiveHint: true
  • upcloud_modify_serverChange a server's title, hostname and/or simple-backup schedule.No findings

    Why it is in this group

    • The name "upcloud_modify_server" says "modify": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Rename a server / set its backup schedule
    • destructiveHint: true
  • upcloud_restart_serverDISRUPTIVE: stop and start a running server.No findings

    Why it is in this group

    • The name "upcloud_restart_server" says "restart": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Restart a server
    • destructiveHint: true
  • upcloud_start_serverStart a stopped server (billing for a started server resumes).No findings

    Why it is in this group

    • The name "upcloud_start_server" says "start": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Start a server
    • destructiveHint: true
  • upcloud_stop_serverDISRUPTIVE: stop a running server — it goes offline until started again with upcloud_start_server.No findings

    Why it is in this group

    • The name "upcloud_stop_server" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Stop a server
    • destructiveHint: true
Only reads 17Show 17 read-only tools
  • upcloud_get_accountThe calling account: username, remaining credits and resource limits (cores, memory, storage per tier, IPs, networks, managed services).No findings

    Why it is in this group

    • The name "upcloud_get_account" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get account
    • readOnlyHint: true
  • upcloud_get_billing_summaryBilling summary for one month with per-resource details (servers, storages, managed databases, object storage, …: amount, hours, plan, zone, labels) and totals.Reads private dataNo findings

    Why it is in this group

    • The name "upcloud_get_billing_summary" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "database": it reads databases.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get monthly billing summary
    • readOnlyHint: true
  • upcloud_get_serverFull 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 remo…No findings

    Why it is in this group

    • The name "upcloud_get_server" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get server details
    • readOnlyHint: true
  • upcloud_get_storageDetails of one storage: size, tier, state (e.g.No findings

    Why it is in this group

    • The name "upcloud_get_storage" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get storage details
    • readOnlyHint: true
  • upcloud_list_audit_logsSecurity audit trail of the account (up to 180 days): who did what to which resource, when, from which IP and via API or Hub.No findings

    Why it is in this group

    • The name "upcloud_list_audit_logs" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List audit logs
    • readOnlyHint: true
  • upcloud_list_databasesManaged Database services (PostgreSQL, MySQL, Valkey, OpenSearch): uuid, title, type, plan, zone, state, component hosts/ports, backups and labels.Reads private data1 finding

    Why it is in this group

    • The name "upcloud_list_databases" says "list": a word for reading.

    What it can reach

    • private-dataThe name "upcloud_list_databases" says "list" and "database": it reads databases.
    • private-dataThe description's first sentence says "database": it reads databases.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...sponse can include connection URIs with credentials. UpCloud: GET /1.3/database."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List managed databases
    • readOnlyHint: true
  • upcloud_list_firewall_rulesThe firewall rules of one server in evaluation order (position, direction, action, family, protocol, address and port ranges, comment).Reads text others writeNo findings

    Why it is in this group

    • The name "upcloud_list_firewall_rules" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List server firewall rules
    • readOnlyHint: true
  • upcloud_list_ip_addressesEvery 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.No findings

    Why it is in this group

    • The name "upcloud_list_ip_addresses" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List IP addresses
    • readOnlyHint: true
  • upcloud_list_kubernetes_clustersManaged Kubernetes clusters: name, uuid, zone, plan, state, network/CIDR, control-plane IP filter, labels and node groups (plan, count, state).No findings

    Why it is in this group

    • The name "upcloud_list_kubernetes_clusters" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Kubernetes clusters
    • readOnlyHint: true
  • upcloud_list_load_balancersManaged Load Balancer services with their frontends, backends and members, networks, plan, zone, configured status and operational state.No findings

    Why it is in this group

    • The name "upcloud_list_load_balancers" says "list": a word for reading.
    Description, as the server wrote it
    Managed Load Balancer services with their frontends, backends and members, networks, plan, zone, configured status and operational state. UpCloud: GET /1.3/load-balancer.

    Annotations the server declares

    • title: List managed load balancers
    • readOnlyHint: true
  • upcloud_list_networksNetworks visible to the account — public, utility and private SDN networks — with their IP subnets, DHCP settings, routes, attached servers and peerings.No findings

    Why it is in this group

    • The name "upcloud_list_networks" says "list": a word for reading.
    Description, as the server wrote it
    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/.

    Annotations the server declares

    • title: List networks
    • readOnlyHint: true
  • upcloud_list_object_storagesManaged Object Storage (S3-compatible) services: uuid, name, region, configured status and operational state, public/private endpoints, custom domains and labels.No findings

    Why it is in this group

    • The name "upcloud_list_object_storages" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List managed object storages
    • readOnlyHint: true
  • upcloud_list_plansFixed-price server plans: name (e.g.No findings

    Why it is in this group

    • The name "upcloud_list_plans" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List server plans
    • readOnlyHint: true
  • upcloud_list_pricesThe price list per zone in the account's currency: per-hour prices for plans, cores, memory, storage tiers, backups, IPv4 addresses and traffic.No findings

    Why it is in this group

    • The name "upcloud_list_prices" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List prices
    • readOnlyHint: true
  • upcloud_list_serversCloud servers on the account (summary: uuid, title, hostname, zone, plan, cores, memory, state, tags, labels).No findings

    Why it is in this group

    • The name "upcloud_list_servers" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List servers
    • readOnlyHint: true
  • upcloud_list_storagesStorage devices: disks, backups, CD-ROM images and OS templates (uuid, title, type, tier, size GB, state, zone, labels).No findings

    Why it is in this group

    • The name "upcloud_list_storages" says "list": a word for reading.
    Description, as the server wrote it
    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}].

    Annotations the server declares

    • title: List storages
    • readOnlyHint: true
  • upcloud_list_zonesAvailable zones (data centres) with id (e.g.No findings

    Why it is in this group

    • The name "upcloud_list_zones" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List zones
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://upcloud.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://upcloud.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://upcloud.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://upcloud.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__upcloud__upcloud_get_account",
      "mcp__upcloud__upcloud_list_zones",
      "mcp__upcloud__upcloud_list_plans",
      "mcp__upcloud__upcloud_list_prices",
      "mcp__upcloud__upcloud_get_billing_summary",
      "mcp__upcloud__upcloud_list_servers",
      "mcp__upcloud__upcloud_get_server",
      "mcp__upcloud__upcloud_list_storages",
      "mcp__upcloud__upcloud_get_storage",
      "mcp__upcloud__upcloud_list_ip_addresses",
      "mcp__upcloud__upcloud_list_firewall_rules",
      "mcp__upcloud__upcloud_list_networks",
      "mcp__upcloud__upcloud_list_databases",
      "mcp__upcloud__upcloud_list_load_balancers",
      "mcp__upcloud__upcloud_list_kubernetes_clusters",
      "mcp__upcloud__upcloud_list_object_storages",
      "mcp__upcloud__upcloud_list_audit_logs"
    ],
    "ask": [],
    "deny": [
      "mcp__upcloud__upcloud_start_server",
      "mcp__upcloud__upcloud_stop_server",
      "mcp__upcloud__upcloud_restart_server",
      "mcp__upcloud__upcloud_create_storage_backup",
      "mcp__upcloud__upcloud_modify_server"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as upcloud. Review it before you use it.

Capability tags behind 3 rules
  • mcp__upcloud__upcloud_get_billing_summary private-data
  • mcp__upcloud__upcloud_list_firewall_rules untrusted-input
  • mcp__upcloud__upcloud_list_databases private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/upcloud/verify?hash=d768cf137b8bea7957e4303d3cc6a6a8cb1c7064196fc5d13578dc5282580eaa" | jq -e '.changed == false'

Pinned hash d768cf137b8b, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/upcloud/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/upcloud
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/upcloud.svg)](https://radar.anlyon.com/servers/io.usefulapi/upcloud)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

UpCloud MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the UpCloud MCP by usefulapi safe?

No scan can promise that. What its definitions show: 22 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the UpCloud MCP by usefulapi delete data?

Yes. 5 tools can delete, cancel or revoke something: upcloud_start_server, upcloud_stop_server, upcloud_restart_server, upcloud_create_storage_backup and upcloud_modify_server.

Can the UpCloud MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the UpCloud MCP by usefulapi have?

22 tools: 5 destructive, 17 read. upcloud_start_server, upcloud_stop_server, upcloud_restart_server, upcloud_create_storage_backup, upcloud_modify_server, upcloud_get_account, upcloud_list_zones, upcloud_list_plans and 14 more.

Does the UpCloud MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the UpCloud MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the UpCloud MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.