← searxng-http-mcp@1.2.1

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 79 · Caution

Evidence

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

Diff · removes 10 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -328,1 +328,0 @@
-<summary><img src="assets/icons/claude.svg" height="16" alt="Claude"> <b>Claude Desktop</b></summary> **Server mode** — edit `~/Library/Application Support/Clau
@@ -375,1 +374,0 @@
-<summary><img src="assets/icons/claude.svg" height="16" alt="Claude"> <b>Claude Code</b></summary> **Server mode**: ```bash claude mcp add --transport http --he
@@ -398,1 +396,0 @@
-<summary><img src="assets/icons/codex.svg" height="16" alt="Codex"> <b>Codex</b></summary> **Server mode** — add to `~/.codex/config.toml`: ```toml [mcp_servers
@@ -427,1 +424,0 @@
-<summary><img src="assets/icons/cursor.svg" height="16" alt="Cursor"> <b>Cursor</b></summary> **Server mode** — edit `.cursor/mcp.json`: ```json { "mcpServers":
@@ -474,1 +470,0 @@
-<summary><img src="assets/icons/githubcopilot.svg" height="16" alt="Copilot"> <b>VS Code Copilot</b></summary> **Server mode** — add to `.vscode/mcp.json`: ```j
diff --git a/README.zh-CN.md b/README.zh-CN.md
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -168,1 +168,0 @@
-<summary>为什么工具更少?</summary> MCP 的设计哲学是组合 — 客户端连接多个专用 server,每个做好一件事。一些竞品把 URL 抓取、渲染提取、多查询并行或研究模式塞进搜索 server。我们有意将工具面控制在三个(搜索、自动补全、引擎发现): - **URL 抓取是独立关注点。** MCP
@@ -328,1 +327,0 @@
-<summary><img src="assets/icons/claude.svg" height="16" alt="Claude"> <b>Claude Desktop</b></summary> **服务器模式** —— 编辑 `~/Library/Application Support/Claude/clau
@@ -377,1 +375,0 @@
-<summary><img src="assets/icons/claude.svg" height="16" alt="Claude"> <b>Claude Code</b></summary> **服务器模式**: ```bash claude mcp add --transport http --header "
@@ -400,1 +397,0 @@
-<summary><img src="assets/icons/codex.svg" height="16" alt="Codex"> <b>Codex</b></summary> **服务器模式** —— 添加到 `~/.codex/config.toml`: ```toml [mcp_servers.searxng
@@ -429,1 +425,0 @@
-<summary><img src="assets/icons/cursor.svg" height="16" alt="Cursor"> <b>Cursor</b></summary> **服务器模式** —— 编辑 `.cursor/mcp.json`: ```json { "mcpServers": { "sea

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) 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/pypi/searxng-http-mcp/1.2.1

## Findings with a location
- `README.md:328` · Collapsed <details> block carrying instructions — README.md:328 · Collapsed <details> block carrying instructions
- `README.md:427` · Collapsed <details> block carrying instructions — README.md:427 · Collapsed <details> block carrying instructions
- `README.md:474` · Collapsed <details> block carrying instructions — README.md:474 · Collapsed <details> block carrying instructions
- `README.zh-CN.md:429` · Collapsed <details> block carrying instructions — README.zh-CN.md:429 · Collapsed <details> block carrying instructions
- `README.zh-CN.md:168` · Collapsed <details> block carrying instructions — README.zh-CN.md:168 · Collapsed <details> block carrying instructions
- `README.md:398` · Collapsed <details> block carrying instructions — README.md:398 · Collapsed <details> block carrying instructions
- `README.md:375` · Collapsed <details> block carrying instructions — README.md:375 · Collapsed <details> block carrying instructions
- `README.zh-CN.md:400` · Collapsed <details> block carrying instructions — README.zh-CN.md:400 · Collapsed <details> block carrying instructions
- `README.zh-CN.md:328` · Collapsed <details> block carrying instructions — README.zh-CN.md:328 · Collapsed <details> block carrying instructions
- `README.zh-CN.md:377` · Collapsed <details> block carrying instructions — README.zh-CN.md:377 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 10 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._
# or from a terminal, under your own account:
gh repo fork whw23/searxng_http_mcp --clone && cd searxng_http_mcp
curl -s https://killerskills.ai/skills/pypi/searxng-http-mcp/1.2.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.2.1 && git commit -am "searxng-http-mcp: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/searxng-http-mcp/1.2.1/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.