upcloud

Tools

22 tools: 17 read-only, 0 change data, 5 high risk (delete, pay, send or run code).

No tool name points to moving money or changing orders.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 4,435 tokens of tool definitions and a 736 ms handshake.

• high riskupcloud_start_serverStart 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.
• high riskupcloud_stop_serverDISRUPTIVE: 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.
• high riskupcloud_restart_serverDISRUPTIVE: 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.
• high riskupcloud_create_storage_backupTake 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.
• high riskupcloud_modify_serverChange 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}.
• read-onlyupcloud_get_accountThe 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.
• read-onlyupcloud_list_zonesAvailable 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.
• read-onlyupcloud_list_plansFixed-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.
• read-onlyupcloud_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. UpCloud: GET /1.3/price.
• read-onlyupcloud_get_billing_summaryBilling 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}.
• read-onlyupcloud_list_serversCloud 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.
• read-onlyupcloud_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 remote-access settings. UpCloud: GET /1.3/server/{uuid}.
• read-onlyupcloud_list_storagesStorage 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}].
• read-onlyupcloud_get_storageDetails 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}.
• read-onlyupcloud_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. UpCloud: GET /1.3/ip_address.
• read-onlyupcloud_list_firewall_rulesThe 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.
• read-onlyupcloud_list_networksNetworks 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/.
• read-onlyupcloud_list_databasesManaged 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.
• read-onlyupcloud_list_load_balancersManaged Load Balancer services with their frontends, backends and members, networks, plan, zone, configured status and operational state. UpCloud: GET /1.3/load-balancer.
• read-onlyupcloud_list_kubernetes_clustersManaged 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.
• read-onlyupcloud_list_object_storagesManaged 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.
• read-onlyupcloud_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. 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.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-06, 736 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-072026-10-06

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Payments and finance, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/upcloud.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/upcloud.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=upcloud.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/upcloud.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/upcloud.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=upcloud.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.