# io.usefulapi/scalingo (remote · scalingo.usefulapi.io)

Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `scalingo.usefulapi.io`: 73/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-scalingo/scalingo.md), [page](https://verifymcp.io/servers/io-usefulapi-scalingo/scalingo)

## Channel facts

- Endpoint: `https://scalingo.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1925 tokens (~91/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-scalingo https://scalingo.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-scalingo]
url = "https://scalingo.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-scalingo": {
      "type": "remote",
      "url": "https://scalingo.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-scalingo --url https://scalingo.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-scalingo:
    url: "https://scalingo.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-scalingo": {
      "type": "http",
      "url": "https://scalingo.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 72, +14)

- [security improvement] Authorization: unverified → pass
- [functional] Stability: fail → 0.17

### 2026-07-31 (score 58, −11)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 12)

First indexed and scored.

## MCP tools (21)

### `list_apps` (~38 tokens)

List apps

List all Scalingo apps you can access in the current region. Scalingo API: GET /v1/apps. Returns { apps: [...] }.

### `get_app` (~67 tokens)

Get an app

Fetch a single app's details (region, stack, status, URLs, flags). Scalingo API: GET /v1/apps/{app}. Returns { app }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).

### `list_containers` (~82 tokens)

List containers (formation)

List an app's container formation — the running process types with their amount and size (the current scaling). Scalingo API: GET /v1/apps/{app}/containers. Returns { containers: [{ name, amount, size }] }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).

### `get_app_stats` (~73 tokens)

Get container stats

Real-time per-container resource stats (CPU / memory / swap usage) for an app. Scalingo API: GET /v1/apps/{app}/stats. Returns { stats: [...] }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).

### `list_deployments` (~108 tokens)

List deployments

List an app's deployments (most recent first), paginated. Scalingo API: GET /v1/apps/{app}/deployments. Returns { deployments: [...], meta: { pagination } }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `page` (integer): Page number (1-based) for paginated lists.
- `per_page` (integer): Entries per page (1-100).

### `get_deployment` (~88 tokens)

Get a deployment

Fetch a single deployment's details (status, git_ref, pusher, image size, timestamps). Scalingo API: GET /v1/apps/{app}/deployments/{deployment_id}. Returns { deployment }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `deployment_id` (string, required): The deployment id.

### `get_app_logs` (~131 tokens)

Get recent app logs

Fetch recent application log lines. Scalingo returns an authenticated logs_url (GET /v1/apps/{app}/logs → { logs_url }); this tool then downloads the last N lines from it (dump mode) and returns them as text. Returns { logs_url, lines }. If the follow-up download fails, only logs_url is returned so you can fetch it yourself.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `lines` (integer): Number of recent log lines to fetch (1-1000, default 100).

### `list_variables` (~82 tokens)

List environment variables

List an app's environment variables. WARNING: this exposes secret VALUES (API keys, database URLs, etc.). Scalingo API: GET /v1/apps/{app}/variables. Returns { variables: [{ id, name, value }] }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).

### `list_collaborators` (~74 tokens)

List collaborators

List an app's collaborators (users invited to the app) and their status. Scalingo API: GET /v1/apps/{app}/collaborators. Returns { collaborators: [...] }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).

### `list_domains` (~67 tokens)

List domains

List an app's custom domains and their TLS/canonical status. Scalingo API: GET /v1/apps/{app}/domains. Returns { domains: [...] }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).

### `list_addons` (~70 tokens)

List addons

List the addons (databases, services) provisioned on an app. Scalingo API: GET /v1/apps/{app}/addons. Returns { addons: [...] }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).

### `list_addon_providers` (~73 tokens)

List addon providers

List the addon providers available on Scalingo (databases, monitoring, etc.) with their plans embedded. Scalingo API: GET /v1/addon_providers. Returns { addon_providers: [{ ..., plans: [...] }] }.

Input parameters:

- `category_id` (string): Optional category id to filter providers.

### `list_app_events` (~136 tokens)

List app events

List an app's activity events (deployments, scaling, restarts, collaborator changes, etc.), paginated. Scalingo API: GET /v1/apps/{app}/events. Returns { events: [...], meta: { pagination } }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `from` (integer): Restrict to events from the last N hours (1-72).
- `page` (integer): Page number (1-based) for paginated lists.
- `per_page` (integer): Entries per page (1-100).

### `get_operation` (~108 tokens)

Get an operation

Poll the status of an asynchronous operation (e.g. a scale or restart returns an operation to track). Scalingo API: GET /v1/apps/{app}/operations/{operation_id}. Returns { operation } with status pending|running|done|error.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `operation_id` (string, required): The operation id (returned in the Location header of a scale/restart response).

### `list_regions` (~59 tokens)

List regions

List the Scalingo regions available to your account, each with its API/dashboard/database hosts. Useful to discover the right SCALINGO_REGION. Scalingo API: GET (auth host) /v1/regions. Returns { regions: [...] }.

### `get_account` (~40 tokens)

Get current account

Fetch the authenticated user's account (id, email, username, fullname, company). Scalingo API: GET /v1/users/self. Returns { user }.

### `scalingo_request` (~153 tokens)

Raw read request

Power-user escape hatch: GET any Scalingo API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Path is taken after /v1 (e.g. "/apps/my-app/alerts"). By default hits the regional API; set on_auth_host:true for auth-host resources (regions, scm_integrations, tokens). Scalingo API: GET {path}.

Input parameters:

- `on_auth_host` (boolean): If true, target the auth host (auth.scalingo.com) instead of the regional API.
- `path` (string, required): API path after /v1, starting with a slash, e.g. "/apps/my-app/notifiers".
- `query` (object): Optional query params object.

### `restart_app` (~111 tokens)

Restart app

MUTATES Scalingo infrastructure — restarts an app's containers. Optionally restart only specific process types via scope; omit scope to restart everything. Returns 202 Accepted (track via get_operation). Scalingo API: POST /v1/apps/{app}/restart.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `scope` (array): Container types to restart, e.g. ["web","worker"]. Omit to restart all.

### `scale_app` (~108 tokens)

Scale app

MUTATES Scalingo infrastructure — sets the container formation (number and/or size of each process type). Only the container types you include are changed. Returns 202 Accepted (track via get_operation). Scalingo API: POST /v1/apps/{app}/scale.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `containers` (array, required): Formation entries to apply. Each entry needs a name plus amount and/or size.

### `set_variables` (~116 tokens)

Set environment variables (bulk)

MUTATES Scalingo infrastructure — creates or updates environment variables in bulk (each { name, value } is created if new or updated if it exists). This usually triggers a restart to apply the new env. Names ≤64 chars, values ≤8192 chars. Scalingo API: PUT /v1/apps/{app}/variables. Returns { variables }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `variables` (array, required): Environment variables to create/update.

### `trigger_deployment` (~141 tokens)

Trigger a deployment

MUTATES Scalingo infrastructure — triggers a new deployment from a source archive URL (a tar.gz reachable by Scalingo). To roll back, re-deploy a previous git_ref/archive — there is no separate rollback endpoint. Scalingo API: POST /v1/apps/{app}/deployments. Returns { deployment }.

Input parameters:

- `app` (string, required): The app name (e.g. my-production-app) or app id (app-…).
- `git_ref` (string): Optional git reference label for the deployment (branch/tag/SHA).
- `source_url` (string, required): URL of the source archive (tar.gz) Scalingo should build and deploy.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-scalingo/scalingo#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 73
- 2026-08-01: 72
- 2026-07-31: 58
- 2026-07-30: 69
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 12

## Links

- Remote endpoint: https://scalingo.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-scalingo/scalingo/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-scalingo/scalingo/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-scalingo/scalingo