Exoscale MCP by usefulapi

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/exoscale and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 10 Oct 2026. Not supplied by the maker.

• exoscale_list_zones

  List the Exoscale zones (data centers) with their API and object-storage endpoints. Compute, storage and network resources live in one zone each. GET /zone.

• exoscale_get_organization

  The Exoscale organization of the API key: id, name, address, country, account balance and currency. GET /organization.

• exoscale_list_quotas

  Resource quotas of the organization: for each resource its current usage and limit (instances, volumes, elastic IPs, and so on). GET /quota.

• exoscale_get_quota

  Usage and limit of one quota entity, for example 'instance'. Use exoscale_list_quotas for the names. GET /quota/{entity}.

• exoscale_get_usage_report

  Aggregated usage of the organization for one month: product, variable, quantity and unit per line. GET /usage-report.

• exoscale_list_instances

  List the compute instances of one zone: id, name, state, instance type, template, IP addresses and security groups. Call once per zone for a full inventory. GET /instance.

• exoscale_get_instance

  Details of one compute instance: state, type, template, disk size, networks, security groups, elastic IPs, snapshots. The cloud-init user-data is never returned. GET /instance/{id}.

• exoscale_start_instance

  WRITE: start a stopped compute instance (normal boot, no rescue profile). Billing for the instance resumes. Returns an operation; poll it with exoscale_get_operation. PUT /instance/{id}:start.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.