← mcp-server@0.7.11

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. 78 · Caution

Evidence

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

Diff · removes 7 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -46,1 +46,0 @@
-<summary>Cursor</summary> [![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](cursor://anysphere.cursor-deeplink/mcp/install?name=CompAi&c
@@ -72,1 +71,0 @@
-<summary>Claude Code CLI</summary> ```bash claude mcp add CompAi -- npx -y @trycompai/mcp-server start --apikey ```
@@ -80,1 +78,0 @@
-<summary>Gemini</summary> ```bash gemini mcp add CompAi -- npx -y @trycompai/mcp-server start --apikey ```
@@ -88,1 +85,0 @@
-<summary>Windsurf</summary> Refer to [Official Windsurf documentation](https://docs.windsurf.com/windsurf/cascade/mcp#adding-a-new-mcp-plugin) for latest inform
@@ -111,1 +107,0 @@
-<summary>VS Code</summary> [![Install in VS Code](https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20CompAi%20MCP&color=0098FF)](vsc
@@ -137,1 +132,0 @@
-<summary> Stdio installation via npm </summary> To start the MCP server, run: ```bash npx @trycompai/mcp-server start --apikey ``` For a full list of server arg
diff --git a/src/landing-page.ts b/src/landing-page.ts
--- a/src/landing-page.ts
+++ b/src/landing-page.ts
@@ -66,1 +66,0 @@
-<link href="https://fonts.googleapis.com/css2?family=Geist+Mono:[email protected]&family=Geist:[email protected]&display=swap" rel="stylesheet">

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

## 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 78/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/mcp-server/0.7.11

## Findings with a location
- `README.md:72` · Collapsed <details> block carrying instructions — README.md:72 · Collapsed <details> block carrying instructions
- `README.md:88` · Collapsed <details> block carrying instructions — README.md:88 · Collapsed <details> block carrying instructions
- `README.md:80` · Collapsed <details> block carrying instructions — README.md:80 · Collapsed <details> block carrying instructions
- `README.md:111` · Collapsed <details> block carrying instructions — README.md:111 · Collapsed <details> block carrying instructions
- `README.md:46` · Collapsed <details> block carrying instructions — README.md:46 · Collapsed <details> block carrying instructions
- `README.md:137` · Collapsed <details> block carrying instructions — README.md:137 · Collapsed <details> block carrying instructions
- `src/landing-page.ts:66` · URL with embedded credentials — src/landing-page.ts:66 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 7 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 trycompai/comp-v2 --clone && cd comp-v2
curl -s https://killerskills.ai/skills/npm/mcp-server/0.7.11/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.7.11 && git commit -am "mcp-server: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/mcp-server/0.7.11/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.