Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/index.mjs b/index.mjs
--- a/index.mjs
+++ b/index.mjs
@@ -1009,1 +1009,0 @@
-"  REVCLAMP_WEBHOOK_SECRET  Synthetic/test webhook secret used by --verify-webhook (never pass secrets in CLI argv).",
@@ -2108,1 +2107,0 @@
-"Error: passing webhook secrets in CLI arguments is forbidden; provide the secret via the REVCLAMP_WEBHOOK_SECRET environment variable."

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.20.32. 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: revclamp-mcp: Credential pass-through configuration (KillerSkills verdict caution 77)

## 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 **CAUTION 77/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/revclamp-mcp/1.20.32

## Findings with a location
- `index.mjs:1009` · Credential pass-through configuration — index.mjs:1009 · Credential pass-through configuration — agent relays sensitive credentials
- `index.mjs:2108` · Prompting user to enter sensitive credentials — index.mjs:2108 · Prompting user to enter sensitive credentials — social engineering

## Proposed change
The attached patch removes the 2 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._