Home / MCP registry index / io.usefulapi/upcloud
UpCloud MCP by usefulapi
io.usefulapi/upcloud in the official MCP registry.
Endpoint https://upcloud.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Inspect servers, storage, networks, databases and billing, and start, stop or back up servers.
We read its 22 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
upcloud_get_account upcloud_list_zones upcloud_list_plans upcloud_list_prices upcloud_get_billing_summary upcloud_list_servers upcloud_get_server upcloud_list_storages upcloud_get_storage upcloud_list_ip_addresses upcloud_list_firewall_rules upcloud_list_networks upcloud_list_databases upcloud_list_load_balancers upcloud_list_kubernetes_clusters upcloud_list_object_storages upcloud_list_audit_logs upcloud_start_server upcloud_stop_server upcloud_restart_server upcloud_create_storage_backup upcloud_modify_server
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-upcloud)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.