Scalingo MCP by usefulapi
REMOTE · SCALINGO.USEFULAPI.IO
Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “audit_domains_addons_and_collaborators_of_an_app” functional
- New prompt “check_app_status_containers_and_resource_use” functional
- New prompt “read_recent_app_logs” functional
- New prompt “restart_scale_set_variables_or_deploy_an_app” functional
- New prompt “review_recent_deployments_and_app_events” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 0
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 0
- Server version: 1.27.0 → 1.28.0 functional
- Server version: 1.26.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.25.0 → 1.26.0 functional
- 25 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.3 → 1.23.0 functional
- Server version: 1.22.0 → 1.22.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.21.0 → 1.22.0 functional
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.18.0 → 1.20.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://scalingo.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of scalingo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://scalingo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/scalingo/ |
| http (plaintext) | http://scalingo.usefulapi.io/mcp | Inconclusive | 302 | http://scalingo.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
scalingo_get_account Get current account ~42
Fetch the authenticated user's account (id, email, username, fullname, company). Scalingo API: GET /v1/users/self. Returns { user }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalingo_get_app Get an app ~69
Fetch a single app's details (region, stack, status, URLs, flags). Scalingo API: GET /v1/apps/{app}. Returns { app }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
No output schema declared.
No examples provided.
scalingo_get_app_logs Get recent app logs ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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). |
No output schema declared.
No examples provided.
scalingo_get_app_stats Get container stats ~75
Real-time per-container resource stats (CPU / memory / swap usage) for an app. Scalingo API: GET /v1/apps/{app}/stats. Returns { stats: [...] }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
No output schema declared.
No examples provided.
scalingo_get_deployment Get a deployment ~90
Fetch a single deployment's details (status, git_ref, pusher, image size, timestamps). Scalingo API: GET /v1/apps/{app}/deployments/{deployment_id}. Returns { deployment }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| deployment_id | string | yes | The deployment id. |
No output schema declared.
No examples provided.
scalingo_get_operation Get an operation ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| operation_id | string | yes | The operation id (returned in the Location header of a scale/restart response). |
No output schema declared.
No examples provided.
scalingo_list_addon_providers List addon providers ~75
List the addon providers available on Scalingo (databases, monitoring, etc.) with their plans embedded. Scalingo API: GET /v1/addon_providers. Returns { addon_providers: [{ ..., plans: [...] }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | string | – | Optional category id to filter providers. |
No output schema declared.
No examples provided.
scalingo_list_addons List addons ~72
List the addons (databases, services) provisioned on an app. Scalingo API: GET /v1/apps/{app}/addons. Returns { addons: [...] }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
No output schema declared.
No examples provided.
scalingo_list_app_events List app events ~138
List an app's activity events (deployments, scaling, restarts, collaborator changes, etc.), paginated. Scalingo API: GET /v1/apps/{app}/events. Returns { events: [...], meta: { pagination } }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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). |
No output schema declared.
No examples provided.
scalingo_list_apps List apps ~40
List all Scalingo apps you can access in the current region. Scalingo API: GET /v1/apps. Returns { apps: [...] }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalingo_list_collaborators List collaborators ~76
List an app's collaborators (users invited to the app) and their status. Scalingo API: GET /v1/apps/{app}/collaborators. Returns { collaborators: [...] }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
No output schema declared.
No examples provided.
scalingo_list_containers List containers (formation) ~84
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 }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
No output schema declared.
No examples provided.
scalingo_list_deployments List deployments ~110
List an app's deployments (most recent first), paginated. Scalingo API: GET /v1/apps/{app}/deployments. Returns { deployments: [...], meta: { pagination } }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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). |
No output schema declared.
No examples provided.
scalingo_list_domains List domains ~69
List an app's custom domains and their TLS/canonical status. Scalingo API: GET /v1/apps/{app}/domains. Returns { domains: [...] }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
No output schema declared.
No examples provided.
scalingo_list_regions List regions ~61
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: [...] }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalingo_list_variables List environment variables ~84
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 }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
No output schema declared.
No examples provided.
scalingo_request Raw read request ~153
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| on_auth_host | boolean | – | If true, target the auth host (auth.scalingo.com) instead of the regional API. |
| path | string | yes | API path after /v1, starting with a slash, e.g. "/apps/my-app/notifiers". |
| query | object | – | Optional query params object. |
No output schema declared.
No examples provided.
scalingo_restart_app Restart app ~115
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 scalingo_get_operation). Scalingo API: POST /v1/apps/{app}/restart.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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. |
No output schema declared.
No examples provided.
scalingo_scale_app Scale app ~112
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 scalingo_get_operation). Scalingo API: POST /v1/apps/{app}/scale.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| containers | array | yes | Formation entries to apply. Each entry needs a name plus amount and/or size. |
No output schema declared.
No examples provided.
scalingo_set_variables Set environment variables (bulk) ~118
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| variables | array | yes | Environment variables to create/update. |
No output schema declared.
No examples provided.
scalingo_trigger_deployment Trigger a deployment ~143
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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 | yes | URL of the source archive (tar.gz) Scalingo should build and deploy. |
No output schema declared.
No examples provided.
How do I install the Scalingo MCP by usefulapi server?
Scalingo MCP by usefulapi is a hosted endpoint at https://scalingo.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · scalingo.usefulapi.io
claude mcp add --transport http io-usefulapi-scalingo 'https://scalingo.usefulapi.io/mcp'
What is the Scalingo MCP by usefulapi server?
Scalingo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/scalingo. Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant. This page covers its hosted endpoint (https://scalingo.usefulapi.io/mcp).
Is the Scalingo MCP by usefulapi server safe to use?
Scalingo MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Scalingo MCP by usefulapi server expose?
Scalingo MCP by usefulapi exposes 21 tools: scalingo_list_apps, scalingo_get_app, scalingo_list_containers, scalingo_get_app_stats, scalingo_list_deployments, and 16 more. Their descriptions and schemas cost roughly 1,969 tokens of context every time the server is loaded.
Does the Scalingo MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Scalingo MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Scalingo MCP by usefulapi server still maintained?
Scalingo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Scalingo MCP by usefulapi server?
VerifyMCP ran 4 checks on Scalingo MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Scalingo MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.