@masonator/coolify-mcp

MCPattested
v2.19.4io.github.StuMasonUnknownUpdated 6d agonpmGitHub

44 optimized tools for managing Coolify infrastructure, diagnostics, and docs search

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
6d agoLast update
Needs 1 credential before it runs
  • COOLIFY_ACCESS_TOKENAPI keyrequired

    Your Coolify API access token

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.StuMason
LicenseUnknown
Version2.19.4
Sourcenpm+mcp-registry
npm@masonator/coolify-mcp
GitHubStuMason/coolify-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 438b803
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan⚠ Warnings (0)v2.19.3 · 12d agoHow well does this scan work?
CHANGEtool-addedTool surface grew since v2.14.1: added renamed
EvalsNone
IndexedJul 12, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagev2.19.3 · 12d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Surface history
CHANGETool surface grew since v2.14.1: added renamed
test-projectNo description published

This tool published no description. Forge does not invent one.

updated-appNo description published

This tool published no description. Forge does not invent one.

nbg1No description published

This tool published no description. Forge does not invent one.

renamedNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

44 optimized tools for managing Coolify infrastructure, diagnostics, and docs search

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

4 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.