Coolify MCP
MCP server for Coolify — 42 optimized tools for managing self-hosted PaaS through AI assistants
Is Coolify MCP safe? Strong public trust posture, backed by multiple independent signals.
Compare Coolify MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Coolify MCP scores 85.5/100 (Grade A), ranked #77 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.1/10; 99% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Coolify MCP compares in MCP Servers
- #23 DaVinci Resolve MCP 85.7 +0.2
- #24 Windows MCP 85.5 ±0
- #25 Coolify MCP 85.5 this agent
- #26 Easyeda MCP Pro 85.4 −0.1
- #27 Browserstack MCP Server 85.2 −0.3
Bars show each HVTrust score; the tick marks Coolify MCP’s 85.5.
Where the 85.5 comes from
HVTrust dimensions vs the MCP Servers average
85.5 / 100 · 100.0% confidenceCoolify MCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
75.1 / 100Supply Chain Trust
Common questions about Coolify MCP
Does Coolify MCP publish package provenance?
Does Coolify MCP have an OpenSSF Scorecard?
Is Coolify MCP actively maintained?
What license does Coolify MCP use?
Are Coolify MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Coolify MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Coolify MCP?
For maintainers
HVTrust scores Coolify MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/coolify-mcp)
<a href="https://hvtracker.net/agents/coolify-mcp"><img src="https://hvtracker.net/badge/coolify-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON