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
@@ -270,1 +270,0 @@
-<summary><strong>Local pip HTTP </strong></summary> > "agent" refers to claude, gemini (agy), grok, qwen, or any MCP client. Codex uses --url instead of --trans
@@ -288,1 +287,0 @@
-<summary><strong>Local pip STDIO</strong></summary> ```bash pip install marm-mcp-server python -m marm_mcp_server.server_stdio # most agents use this --transpor
@@ -412,1 +410,0 @@
-<summary><strong>Docker HTTP swarm mode</strong></summary> ```bash # --swarm: write queue on, 200 RPM - recommended for multi-agent shared servers docker run -d
@@ -427,1 +424,0 @@
-<summary><strong>Docker graph indexing: mount the repo</strong></summary> Docker graph tools run inside the container, so they cannot see host paths unless you 
@@ -455,1 +451,0 @@
-<summary><strong>Docker STDIO (no HTTP key)</strong></summary> Docker STDIO includes the same built-in marm-graph tools; no extra image or install step is requi

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 66/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/marm-mcp-server/2.60.1

## Findings with a location
- `README.md:455` · Collapsed <details> block carrying instructions — README.md:455 · Collapsed <details> block carrying instructions
- `README.md:427` · Collapsed <details> block carrying instructions — README.md:427 · Collapsed <details> block carrying instructions
- `README.md:270` · Collapsed <details> block carrying instructions — README.md:270 · Collapsed <details> block carrying instructions
- `README.md:412` · Collapsed <details> block carrying instructions — README.md:412 · Collapsed <details> block carrying instructions
- `README.md:288` · Collapsed <details> block carrying instructions — README.md:288 · Collapsed <details> block carrying instructions

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