Propose a patch

Evidence

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

diff --git a/dist/cli.js b/dist/cli.js
--- a/dist/cli.js
+++ b/dist/cli.js
@@ -3739,1 +3739,0 @@
-<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=JetBrains+Mono:wght@400;500;600&display=swap" rel="stylesheet"/>
diff --git a/dist/index.js b/dist/index.js
--- a/dist/index.js
+++ b/dist/index.js
@@ -3498,1 +3498,0 @@
-<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=JetBrains+Mono:wght@400;500;600&display=swap" rel="stylesheet"/>
diff --git a/src/veyaPage.ts b/src/veyaPage.ts
--- a/src/veyaPage.ts
+++ b/src/veyaPage.ts
@@ -142,1 +142,0 @@
-<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=JetBrains+Mono:wght@400;500;600&display=swap" rel="stylesheet"/>

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.13. 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: mcp: URL with embedded credentials (KillerSkills verdict caution 79)

## 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 79/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/mcp/1.2.13

## Findings with a location
- `dist/cli.js:3739` · URL with embedded credentials — dist/cli.js:3739 · URL with embedded credentials — may be phishing or credential leaking
- `dist/index.js:3498` · URL with embedded credentials — dist/index.js:3498 · URL with embedded credentials — may be phishing or credential leaking
- `src/veyaPage.ts:142` · URL with embedded credentials — src/veyaPage.ts:142 · URL with embedded credentials — may be phishing or credential leaking

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