Propose a patch

Evidence

• Contacted office-mcp-production.up.railway.app: not declared and not needed for the documented job.

diff --git a/unconfigure.js b/unconfigure.js
--- a/unconfigure.js
+++ b/unconfigure.js
@@ -24,1 +24,0 @@
-const code = text.replace(/^/, ' ').split('')
@@ -364,1 +363,0 @@
-const bom = text.startsWith('') ? '' : ''
@@ -519,1 +517,0 @@
-// left on Windows: the relay token and the device key in the Credential Manager, %APPDATA%\Local MCP,
diff --git a/link.js b/link.js
--- a/link.js
+++ b/link.js
@@ -228,1 +228,0 @@
-// lmcp-api#761 §1–2: before link, the binary registers the machine's relay token (without opening the
@@ -230,1 +229,0 @@
-// first_seen exists. The binary keeps the token where it keeps its relay token: the answer never carries it.
diff --git a/download.js b/download.js
--- a/download.js
+++ b/download.js
@@ -116,1 +116,0 @@
-// The go-server reads its relay token ONLY from getCacheDir()/.cloud-token, a plain trimmed string
@@ -247,1 +246,0 @@
-//   2. the Go client's store; 3. no store and a relay token: the value a 3.0.420 client reports
diff --git a/setup.js b/setup.js
--- a/setup.js
+++ b/setup.js
@@ -482,1 +482,0 @@
-// lmcp-api#761 §1–2: the binary registers this installation's relay token (no tunnel) and beats once,
@@ -594,1 +593,0 @@
-// lmcp-npm#141, lmcp-api#761: Node registers no relay token and writes none. The binary does it
@@ -596,1 +594,0 @@
-// relay token; the tunnel only comes up after approval. A token that already exists is kept: setup
diff --git a/index.js b/index.js
--- a/index.js
+++ b/index.js
@@ -352,1 +352,0 @@
-// #144: without the app, also the relay token, the device key, the Roaming config, logs and caches.

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.0.446. 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: local-mcp: Contacted office-mcp-production.up.railway.app: not declared and not needed for the documented job (KillerSkills verdict blocked 45)

## 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 45/100**. Summary: sends data to office-mcp-production.up.railway.app.

- Contacted office-mcp-production.up.railway.app: not declared and not needed for the documented job.

Full trace and findings: https://killerskills.ai/skills/npm/local-mcp/3.0.446

## Findings with a location
- `unconfigure.js:519` · Credential pass-through configuration — unconfigure.js:519 · Credential pass-through configuration — agent relays sensitive credentials
- `link.js:230` · Credential pass-through configuration — link.js:230 · Credential pass-through configuration — agent relays sensitive credentials
- `download.js:116` · Credential pass-through configuration — download.js:116 · Credential pass-through configuration — agent relays sensitive credentials
- `setup.js:596` · Credential pass-through configuration — setup.js:596 · Credential pass-through configuration — agent relays sensitive credentials
- `index.js:352` · Credential pass-through configuration — index.js:352 · Credential pass-through configuration — agent relays sensitive credentials
- `unconfigure.js:24` · Hidden zero-width characters detected — unconfigure.js:24 · Hidden zero-width characters detected — may conceal content
- `download.js:247` · Credential pass-through configuration — download.js:247 · Credential pass-through configuration — agent relays sensitive credentials
- `unconfigure.js:364` · Hidden zero-width characters detected — unconfigure.js:364 · Hidden zero-width characters detected — may conceal content
- `setup.js:482` · Credential pass-through configuration — setup.js:482 · Credential pass-through configuration — agent relays sensitive credentials
- `setup.js:594` · Credential pass-through configuration — setup.js:594 · Credential pass-through configuration — agent relays sensitive credentials
- `link.js:228` · Credential pass-through configuration — link.js:228 · 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._