Propose a patch

Evidence

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

diff --git a/dist/src/handlers/team.js b/dist/src/handlers/team.js
--- a/dist/src/handlers/team.js
+++ b/dist/src/handlers/team.js
@@ -44,1 +44,0 @@
-…erve (free, local, no key needed)"},gemini:{key:"GEMINI_API_KEY",hint:"Get at: https://aistudio.google.com/app/apikey"}},i=e[a]??e.openai,l=!!o.vector_token,u=JSON.stringify({mcpServers:{cachly:{command:"npx",args:["-y","@cachly-dev/mcp-server@latest"],env:{CACHLY_JWT:"your-api-token-from-cachly.dev/s…
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -440,1 +440,0 @@
-<summary><b>Claude Code</b> (<code>.mcp.json</code> in the project)</summary> ```json { "mcpServers": { "cachly": { "command": "npx", "args": ["-y", "@cachly-de

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

## 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 67/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-server/0.10.250

## Findings with a location
- `dist/src/handlers/team.js:44` · URL with embedded credentials — dist/src/handlers/team.js:44 · URL with embedded credentials — may be phishing or credential leaking
- `README.md:440` · Collapsed <details> block carrying instructions — README.md:440 · Collapsed <details> block carrying instructions

## 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._