ToolsMCP
Exoscale MCP Server
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- samisouabni (GitHub)
- Prerequisites
- Install @samisouabni/exoscale-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.0.4 · updated
Publisher’s description
MCP server for managing Exoscale cloud infrastructure — compute, Kubernetes, DNS, databases, storage
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.4, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- samisouabni (GitHub)
- Version observed
- 1.0.4
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.samisouabni%2Fexoscale-mcp/versions/1.0.4
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Inspect and manage cloud resources | Publisher description mentions “kubernetes”, “infrastructure”, “dns”. | No connection check or task run. Capability is as described by the publisher. | Rule cloud-infrastructure matched: “kubernetes”, “infrastructure”, “dns”. Rule cloud-infrastructure. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@samisouabni/exoscale-mcp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.samisouabni/exoscale-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.