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
@@ -69,1 +69,0 @@
-<summary><b>Claude Code</b></summary> ```bash claude mcp add apify "https://mcp.apify.com" -t http ``` Claude Code opens the Apify sign-in page the first time i
@@ -80,1 +79,0 @@
-<summary><b>ChatGPT</b></summary> 1. Open [ChatGPT Plugins](https://chatgpt.com/plugins), select **+**, then **Add custom MCP server**. 2. Name it `Apify`, ente
@@ -95,1 +93,0 @@
-<summary><b>Cursor</b></summary> Use the one-click install link from the [configurator](https://mcp.apify.com), or let the [Apify CLI](https://docs.apify.com/cl
@@ -108,1 +105,0 @@
-<summary><b>VS Code and GitHub Copilot</b></summary> Use the one-click install link from the [configurator](https://mcp.apify.com), run `apify mcp install vscod
@@ -150,1 +146,0 @@
-<summary><b>Local stdio (npx)</b></summary> Requires Node.js 22 or later. ```json { "mcpServers": { "actors-mcp-server": { "command": "npx", "args": ["-y", "@ap
@@ -403,1 +398,0 @@
-<summary><b>How the server adapts Actor input schemas</b></summary> The server adapts Actor input schemas so that more clients and models can use them: - Descri
diff --git a/dist/utils/auth.js b/dist/utils/auth.js
--- a/dist/utils/auth.js
+++ b/dist/utils/auth.js
@@ -27,1 +27,0 @@
-// Only bypass token if all requested tools are public AND no specific actors requested.
diff --git a/dist/mcp/actors.js b/dist/mcp/actors.js
--- a/dist/mcp/actors.js
+++ b/dist/mcp/actors.js
@@ -52,1 +52,0 @@
-// `origin` excludes userinfo, so `https://user:pass@<standby host>/mcp` passes the origin check; drop it here.

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

## 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 69/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/actors-mcp-server/0.21.2

## Findings with a location
- `README.md:150` · Collapsed <details> block carrying instructions — README.md:150 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file
- `README.md:95` · Collapsed <details> block carrying instructions — README.md:95 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file
- `README.md:108` · Collapsed <details> block carrying instructions — README.md:108 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file
- `README.md:403` · Collapsed <details> block carrying instructions — README.md:403 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file
- `dist/utils/auth.js:27` · Credential pass-through configuration — dist/utils/auth.js:27 · Credential pass-through configuration — agent relays sensitive credentials
- `README.md:80` · Collapsed <details> block carrying instructions — README.md:80 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file
- `dist/mcp/actors.js:52` · URL with embedded credentials — dist/mcp/actors.js:52 · URL with embedded credentials — may be phishing or credential leaking
- `README.md:69` · Collapsed <details> block carrying instructions — README.md:69 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file

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