io.usefulapi/scalingo
REMOTE · SCALINGO.USEFULAPI.IO · SCANNED SEP 20
Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.
Available components
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 fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.usefulapi/scalingo MCP server?
io.usefulapi/scalingo 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'
{
"mcpServers": {
"io-usefulapi-scalingo": {
"url": "https://scalingo.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-scalingo": {
"type": "http",
"url": "https://scalingo.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-scalingo] url = "https://scalingo.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-scalingo": {
"type": "remote",
"url": "https://scalingo.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-scalingo --url 'https://scalingo.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-scalingo:
url: "https://scalingo.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-scalingo": {
"Transport": "http",
"Url": "https://scalingo.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-scalingo -t streamable-http -u 'https://scalingo.usefulapi.io/mcp'
{
"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.
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.
- 20 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- 17 Sept 26 −13
- Authorization: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- 13 Sept 26 +58
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 12 Sept 26 −58
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- Authorization: unverified → pass ▲ security
- Stability: fail → 0.17 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 20 Sept 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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c07701466a53a4a30e5706c27de8a19b |
| SANs: usefulapi.io, *.scalingo.usefulapi.io, scalingo.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. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
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 | Auth required | 401 | |
| http (plaintext) | http://scalingo.usefulapi.io/mcp | Inconclusive | 401 |
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 →
get_account Get current account ~40
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.
get_app Get an app ~67
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.
get_app_logs Get recent app logs ~131
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.
get_app_stats Get container stats ~73
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.
get_deployment Get a deployment ~88
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.
get_operation Get an operation ~108
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.
list_addon_providers List addon providers ~73
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.
list_addons List addons ~70
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.
list_app_events List app events ~136
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.
list_apps List apps ~38
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.
list_collaborators List collaborators ~74
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.
list_containers List containers (formation) ~82
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.
list_deployments List deployments ~108
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.
list_domains List domains ~67
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.
list_regions List regions ~59
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.
list_variables List environment variables ~82
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.
restart_app Restart app ~111
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.
| 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.
scale_app Scale app ~108
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.
| 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_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.
set_variables Set environment variables (bulk) ~116
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.
trigger_deployment Trigger a deployment ~141
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.
What is the io.usefulapi/scalingo MCP server?
io.usefulapi/scalingo is an MCP server 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 io.usefulapi/scalingo MCP server safe to use?
io.usefulapi/scalingo 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 io.usefulapi/scalingo MCP server expose?
io.usefulapi/scalingo exposes 21 tools: list_apps, get_app, list_containers, get_app_stats, list_deployments, and 16 more. Their descriptions and schemas cost roughly 1,925 tokens of context every time the server is loaded.
Does the io.usefulapi/scalingo MCP server require authentication?
No. We connected to io.usefulapi/scalingo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.usefulapi/scalingo MCP server still maintained?
io.usefulapi/scalingo is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.