Server providing Argo CD integration for MCP clients.
Nothing to run from here
Scalingo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
21
tools declared
remote
at its publisher
—
calls last 7d
What it does
Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http scalingo-mcp https://scalingo.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# list_apps, get_app, list_containers and 18 more
Scalingo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http scalingo-mcp https://scalingo.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all Scalingo apps you can access in the current region. Scalingo API: GET /v1/apps. Returns { apps: [...] }.
No parameter schema on file.
Fetch a single app's details (region, stack, status, URLs, flags). Scalingo API: GET /v1/apps/{app}. Returns { app }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
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 }] }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
Real-time per-container resource stats (CPU / memory / swap usage) for an app. Scalingo API: GET /v1/apps/{app}/stats. Returns { stats: [...] }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
List an app's deployments (most recent first), paginated. Scalingo API: GET /v1/apps/{app}/deployments. Returns { deployments: [...], meta: { pagination } }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| page | integer | no | Page number (1-based) for paginated lists. |
| per_page | integer | no | Entries per page (1-100). |
Fetch a single deployment's details (status, git_ref, pusher, image size, timestamps). Scalingo API: GET /v1/apps/{app}/deployments/{deployment_id}. Returns { deployment }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| deployment_id | string | yes | The deployment id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| lines | integer | no | Number of recent log lines to fetch (1-1000, default 100). |
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 }] }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
List an app's collaborators (users invited to the app) and their status. Scalingo API: GET /v1/apps/{app}/collaborators. Returns { collaborators: [...] }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
List an app's custom domains and their TLS/canonical status. Scalingo API: GET /v1/apps/{app}/domains. Returns { domains: [...] }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
List the addons (databases, services) provisioned on an app. Scalingo API: GET /v1/apps/{app}/addons. Returns { addons: [...] }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
List the addon providers available on Scalingo (databases, monitoring, etc.) with their plans embedded. Scalingo API: GET /v1/addon_providers. Returns { addon_providers: [{ ..., plans: [...] }] }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | Optional category id to filter providers. |
List an app's activity events (deployments, scaling, restarts, collaborator changes, etc.), paginated. Scalingo API: GET /v1/apps/{app}/events. Returns { events: [...], meta: { pagination } }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| page | integer | no | Page number (1-based) for paginated lists. |
| per_page | integer | no | Entries per page (1-100). |
| from | integer | no | Restrict to events from the last N hours (1-72). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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). |
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: [...] }.
No parameter schema on file.
Fetch the authenticated user's account (id, email, username, fullname, company). Scalingo API: GET /v1/users/self. Returns { user }.
No parameter schema on file.
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | API path after /v1, starting with a slash, e.g. "/apps/my-app/notifiers". |
| query | object | no | Optional query params object. |
| on_auth_host | boolean | no | If true, target the auth host (auth.scalingo.com) instead of the regional API. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| scope | array | no | Container types to restart, e.g. ["web","worker"]. Omit to restart all. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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 }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| variables | array | yes | Environment variables to create/update. |
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 }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app name (e.g. my-production-app) or app id (app-…). |
| source_url | string | yes | URL of the source archive (tar.gz) Scalingo should build and deploy. |
| git_ref | string | no | Optional git reference label for the deployment (branch/tag/SHA). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Scalingo or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digeste406d07d882891ea631ed99fde646d1673e462b102636f81a384e87aa113004e
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_apps | no tags | |
| get_app | untrusted-input | untrusted-input: keyword "fetch" |
| list_containers | no tags | |
| get_app_stats | no tags | |
| list_deployments | no tags | |
| get_deployment | untrusted-input | untrusted-input: keyword "fetch" |
| get_app_logs | untrusted-input | untrusted-input: keyword "fetch" |
| list_variables | no tags | |
| list_collaborators | no tags | |
| list_domains | no tags | |
| list_addons | no tags | |
| list_addon_providers | no tags | |
| list_app_events | no tags | |
| get_operation | no tags | |
| list_regions | no tags | |
| get_account | untrusted-input | untrusted-input: keyword "fetch" |
| scalingo_request | no tags | |
| restart_app | state-write | state-write: declares destructiveHint: true |
| scale_app | state-write | state-write: declares destructiveHint: true |
| set_variables | state-write | state-write: declares destructiveHint: true |
| trigger_deployment | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digeste406d07d882891ea
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Scalingo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.