Propose a patch

Evidence

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

diff --git a/sdk/node/src/launchopts.ts b/sdk/node/src/launchopts.ts
--- a/sdk/node/src/launchopts.ts
+++ b/sdk/node/src/launchopts.ts
@@ -567,1 +567,0 @@
-const { server, username, password } = proxy ? proxyCredentials(proxy) : { server: "", username: "", password: "" };
@@ -587,1 +586,0 @@
-export function proxyCredentials(proxy: PwProxy): { server: string; username: string; password: string } {
@@ -609,1 +607,0 @@
-const { server, username, password } = proxyCredentials(proxy);
diff --git a/sdk/node/src/multiplex.ts b/sdk/node/src/multiplex.ts
--- a/sdk/node/src/multiplex.ts
+++ b/sdk/node/src/multiplex.ts
@@ -7,1 +7,0 @@
-//   chromium.connectOverCDP("http://127.0.0.1:9222?fingerprint=acct-2&proxy=socks5://u:p@host:1080&geoip=true")
@@ -145,1 +144,0 @@
-/** The raw accepted parameters (proxy credentials redacted), for the status page. */
@@ -267,1 +265,0 @@
-/** Canonical form of an identity's launch options (proxy credentials included, never displayed). */
diff --git a/sdk/node/src/cloud.ts b/sdk/node/src/cloud.ts
--- a/sdk/node/src/cloud.ts
+++ b/sdk/node/src/cloud.ts
@@ -54,1 +54,0 @@
-"no Clearcote API key: pass apiKey or set CLEARCOTE_API_KEY (create a key in the Clearcote dashboard)";
diff --git a/sdk/node/src/cli.ts b/sdk/node/src/cli.ts
--- a/sdk/node/src/cli.ts
+++ b/sdk/node/src/cli.ts
@@ -48,1 +48,0 @@
---proxy <url>        proxy, e.g. http://user:pass@host:port
diff --git a/sdk/node/src/reqproxy.ts b/sdk/node/src/reqproxy.ts
--- a/sdk/node/src/reqproxy.ts
+++ b/sdk/node/src/reqproxy.ts
@@ -21,1 +21,0 @@
-import { proxyCredentials, type PwProxy } from "./launchopts.js";
@@ -50,1 +49,0 @@
-const { server, username, password } = proxyCredentials(proxy);
diff --git a/sdk/node/src/index.ts b/sdk/node/src/index.ts
--- a/sdk/node/src/index.ts
+++ b/sdk/node/src/index.ts
@@ -274,1 +274,0 @@
-/** Keep the persona switches (seed, overrides, proxy credentials, canvas-bridge token) off the

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

## What the honeypot observed
KillerSkills ran **clearcote-mcp@r1** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 68/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/clearcote-mcp/r1

## Findings with a location
- `sdk/node/src/launchopts.ts:567` · Credential pass-through configuration — sdk/node/src/launchopts.ts:567 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/multiplex.ts:7` · URL with embedded credentials — sdk/node/src/multiplex.ts:7 · URL with embedded credentials — may be phishing or credential leaking
- `sdk/node/src/cloud.ts:54` · Credential pass-through configuration — sdk/node/src/cloud.ts:54 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/cli.ts:48` · URL with embedded credentials — sdk/node/src/cli.ts:48 · URL with embedded credentials — may be phishing or credential leaking
- `sdk/node/src/multiplex.ts:145` · Credential pass-through configuration — sdk/node/src/multiplex.ts:145 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/reqproxy.ts:50` · Credential pass-through configuration — sdk/node/src/reqproxy.ts:50 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/launchopts.ts:587` · Credential pass-through configuration — sdk/node/src/launchopts.ts:587 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/index.ts:274` · Credential pass-through configuration — sdk/node/src/index.ts:274 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/reqproxy.ts:21` · Credential pass-through configuration — sdk/node/src/reqproxy.ts:21 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/multiplex.ts:267` · Credential pass-through configuration — sdk/node/src/multiplex.ts:267 · Credential pass-through configuration — agent relays sensitive credentials
- `sdk/node/src/launchopts.ts:609` · Credential pass-through configuration — sdk/node/src/launchopts.ts:609 · Credential pass-through configuration — agent relays sensitive credentials

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