← coolify-mcp@3.10.1

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 47 · Blocked

Evidence

  • Contacted localhost: not declared and not needed for the documented job.

Diff · removes 4 caught lines

Download .patch
diff --git a/dist/lib/startup-check.js b/dist/lib/startup-check.js
--- a/dist/lib/startup-check.js
+++ b/dist/lib/startup-check.js
@@ -226,1 +226,0 @@
-'Re-paste the token without it.');
@@ -230,1 +229,0 @@
-'Coolify rejects every request with 401. Re-paste the token without it.');
diff --git a/dist/__tests__/ssrf.test.js b/dist/__tests__/ssrf.test.js
--- a/dist/__tests__/ssrf.test.js
+++ b/dist/__tests__/ssrf.test.js
@@ -41,1 +41,0 @@
-'https://user:[email protected]/x',
diff --git a/dist/__tests__/oauth.test.js b/dist/__tests__/oauth.test.js
--- a/dist/__tests__/oauth.test.js
+++ b/dist/__tests__/oauth.test.js
@@ -943,1 +943,0 @@
-['https://user:[email protected]/client.json', 'userinfo'],

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.10.1. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: coolify-mcp: Contacted localhost: not declared and not needed for the documented job (KillerSkills verdict blocked 47)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **BLOCKED 47/100**. Summary: sends data to localhost.

- Contacted localhost: not declared and not needed for the documented job.

Full trace and findings: https://killerskills.ai/skills/npm/coolify-mcp/3.10.1

## Findings with a location
- `dist/lib/startup-check.js:226` · Prompting user to enter sensitive credentials — dist/lib/startup-check.js:226 · Prompting user to enter sensitive credentials — social engineering
- `dist/__tests__/ssrf.test.js:41` · URL with embedded credentials — dist/__tests__/ssrf.test.js:41 · URL with embedded credentials — may be phishing or credential leaking
- `dist/__tests__/oauth.test.js:943` · URL with embedded credentials — dist/__tests__/oauth.test.js:943 · URL with embedded credentials — may be phishing or credential leaking
- `dist/lib/startup-check.js:230` · Prompting user to enter sensitive credentials — dist/lib/startup-check.js:230 · Prompting user to enter sensitive credentials — social engineering

## Proposed change
The attached patch removes the 4 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._
# or from a terminal, under your own account:
gh repo fork StuMason/coolify-mcp --clone && cd coolify-mcp
curl -s https://killerskills.ai/skills/npm/coolify-mcp/3.10.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/3.10.1 && git commit -am "coolify-mcp: Contacted localhost: not declared and not needed for the documented job"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/coolify-mcp/3.10.1/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.