Propose a patch

Evidence

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

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -99,1 +99,0 @@
-<summary>Using docker</summary> ```json { "mcpServers": { "fetch": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/fetch"] } } } ```
@@ -160,1 +159,0 @@
-<summary>Using Docker</summary> ```json { "mcp": { "servers": { "fetch": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/fetch"] } } } } ```
diff --git a/tests/test_non_cp1252_pages.py b/tests/test_non_cp1252_pages.py
--- a/tests/test_non_cp1252_pages.py
+++ b/tests/test_non_cp1252_pages.py
@@ -24,1 +24,0 @@
-BOM = ""

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2026.11.4. 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-fetch: Collapsed <details> block carrying instructions (KillerSkills verdict caution 59)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8) and scored it **CAUTION 59/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mcp-server-fetch/2026.11.4

## Findings with a location
- `README.md:160` · Collapsed <details> block carrying instructions — README.md:160 · Collapsed <details> block carrying instructions
- `README.md:99` · Collapsed <details> block carrying instructions — README.md:99 · Collapsed <details> block carrying instructions
- `tests/test_non_cp1252_pages.py:24` · Hidden zero-width characters detected — tests/test_non_cp1252_pages.py:24 · Hidden zero-width characters detected — may conceal content

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