Coolify (pashvc) MCP Server

@pashvc/mcp-server-coolify npm v1.0.1

Published by @pashvc — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Coolify API integration with comprehensive resource management

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 14

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([get_application_logs]) and tools that can send data out ([create_application, update_application, execute_command, deploy_webhook]) are exposed together. An agent can move private data to the sink.

Evidence: sources [get_application_logs] → sinks [create_application, update_application, execute_command, deploy_webhook]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow get_application_logs → create_application

high Tool "create_application" exposes command/code executionMTC-CAP-001

Tool "create_application" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool create_application

high Tool "update_application" exposes command/code executionMTC-CAP-001

Tool "update_application" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool update_application

high Tool "execute_command" exposes command/code executionMTC-CAP-001

Tool "execute_command" appears to run shell commands or evaluate code (keyword "execute command" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool execute_command

medium Unconstrained command parameter "install_command" on "create_application"MTC-CAP-006

Tool "create_application" takes a command-shaped parameter "install_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool create_application · inputSchema.properties.install_command

medium Unconstrained command parameter "build_command" on "create_application"MTC-CAP-006

Tool "create_application" takes a command-shaped parameter "build_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool create_application · inputSchema.properties.build_command

medium Unconstrained command parameter "start_command" on "create_application"MTC-CAP-006

Tool "create_application" takes a command-shaped parameter "start_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool create_application · inputSchema.properties.start_command

medium Unconstrained command parameter "install_command" on "update_application"MTC-CAP-006

Tool "update_application" takes a command-shaped parameter "install_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool update_application · inputSchema.properties.install_command

medium Unconstrained command parameter "build_command" on "update_application"MTC-CAP-006

Tool "update_application" takes a command-shaped parameter "build_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool update_application · inputSchema.properties.build_command

medium Unconstrained command parameter "start_command" on "update_application"MTC-CAP-006

Tool "update_application" takes a command-shaped parameter "start_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool update_application · inputSchema.properties.start_command

medium Unconstrained command parameter "command" on "execute_command"MTC-CAP-006

Tool "execute_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool execute_command · inputSchema.properties.command

low Mutating tool "create_application" declares no destructiveHintMTC-CAP-005

Tool "create_application" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool create_application

low Mutating tool "update_application" declares no destructiveHintMTC-CAP-005

Tool "update_application" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool update_application

low Mutating tool "execute_command" declares no destructiveHintMTC-CAP-005

Tool "execute_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool execute_command

Tools 53

Each tool and what it can reach — statically extracted from the published source.

  • create_applicationruns code / shell
  • deploy_webhooknetwork egress
  • execute_commandruns code / shell
  • get_application_logsreads sensitive data
  • update_applicationruns code / shell
  • coolify_healthno sensitive capability
  • coolify_versionno sensitive capability
  • create_databaseno sensitive capability
  • create_environment_variableno sensitive capability
  • create_private_keyno sensitive capability
Show 43 more tools ↓
  • create_projectno sensitive capability
  • create_serverno sensitive capability
  • create_serviceno sensitive capability
  • delete_applicationno sensitive capability
  • delete_databaseno sensitive capability
  • delete_environment_variableno sensitive capability
  • delete_private_keyno sensitive capability
  • delete_projectno sensitive capability
  • delete_serviceno sensitive capability
  • get_applicationno sensitive capability
  • get_current_teamno sensitive capability
  • get_current_team_membersno sensitive capability
  • get_databaseno sensitive capability
  • get_deploymentno sensitive capability
  • get_projectno sensitive capability
  • get_server_domainsno sensitive capability
  • get_server_resourcesno sensitive capability
  • get_serviceno sensitive capability
  • get_teamno sensitive capability
  • list_applicationsno sensitive capability
  • list_databasesno sensitive capability
  • list_deploymentsno sensitive capability
  • list_environment_variablesno sensitive capability
  • list_private_keysno sensitive capability
  • list_projectsno sensitive capability
  • list_serversno sensitive capability
  • list_servicesno sensitive capability
  • list_teamsno sensitive capability
  • restart_applicationno sensitive capability
  • restart_databaseno sensitive capability
  • restart_serviceno sensitive capability
  • start_applicationno sensitive capability
  • start_databaseno sensitive capability
  • start_serviceno sensitive capability
  • stop_applicationno sensitive capability
  • stop_databaseno sensitive capability
  • stop_serviceno sensitive capability
  • update_databaseno sensitive capability
  • update_environment_variableno sensitive capability
  • update_private_keyno sensitive capability
  • update_projectno sensitive capability
  • update_serviceno sensitive capability
  • validate_serverno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.1 latest A 93/100 14 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pashvc-mcp-server-coolify/badge.svg)](https://mcptrustchecker.com/registry/pashvc-mcp-server-coolify)
HTML
<a href="https://mcptrustchecker.com/registry/pashvc-mcp-server-coolify"><img src="https://mcptrustchecker.com/registry/pashvc-mcp-server-coolify/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pashvc-mcp-server-coolify/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @pashvc/mcp-server-coolify --online

Use the free API → How scoring works

Other implementations of Coolify 9

Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →

More in Cloud & DevOps