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
@@ -58,1 +58,0 @@
-<summary>Using uvx</summary> ```json "mcpServers": { "sentry": { "command": "uvx", "args": ["mcp-server-sentry", "--auth-token", "YOUR_SENTRY_TOKEN"] } } ```
@@ -71,1 +70,0 @@
-<details> <summary>Using docker</summary> ```json "mcpServers": { "sentry": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/sentry", "--auth-token", "
@@ -86,1 +84,0 @@
-<summary>Using pip installation</summary> ```json "mcpServers": { "sentry": { "command": "python", "args": ["-m", "mcp_server_sentry", "--auth-token", "YOUR_SEN
@@ -104,1 +101,0 @@
-<summary>Using uvx</summary> ```json "context_servers": [ "mcp-server-sentry": { "command": { "path": "uvx", "args": ["mcp-server-sentry", "--auth-token", "YOUR
@@ -119,1 +115,0 @@
-<summary>Using pip installation</summary> ```json "context_servers": { "mcp-server-sentry": { "command": "python", "args": ["-m", "mcp_server_sentry", "--auth-t

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.6.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-sentry-xhs: 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.8.1) and scored it **CAUTION 66/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mcp-server-sentry-xhs/0.6.4

## Findings with a location
- `README.md:86` · Collapsed <details> block carrying instructions — README.md:86 · Collapsed <details> block carrying instructions
- `README.md:58` · Collapsed <details> block carrying instructions — README.md:58 · Collapsed <details> block carrying instructions
- `README.md:119` · Collapsed <details> block carrying instructions — README.md:119 · Collapsed <details> block carrying instructions
- `README.md:71` · Collapsed <details> block carrying instructions — README.md:71 · Collapsed <details> block carrying instructions
- `README.md:104` · Collapsed <details> block carrying instructions — README.md:104 · 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._