Propose a patch

Evidence

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

diff --git a/src/mixcloud_mcp_server/tools/upload.py b/src/mixcloud_mcp_server/tools/upload.py
--- a/src/mixcloud_mcp_server/tools/upload.py
+++ b/src/mixcloud_mcp_server/tools/upload.py
@@ -34,1 +34,0 @@
-from reading e.g. ``~/.ssh/id_rsa``.
diff --git a/tests/test_upload.py b/tests/test_upload.py
--- a/tests/test_upload.py
+++ b/tests/test_upload.py
@@ -23,1 +23,0 @@
-"""The prompt-injection case: a model asking for ~/.ssh/id_rsa."""

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: mixcloud-mcp-server: Reads credential paths from the home directory (KillerSkills verdict caution 71)

## 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 71/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/mixcloud-mcp-server/0.1.1

## Findings with a location
- `src/mixcloud_mcp_server/tools/upload.py:34` · Reads credential paths from the home directory — src/mixcloud_mcp_server/tools/upload.py:34 · Reads credential paths from the home directory
- `tests/test_upload.py:23` · References a credential file in the home directory — tests/test_upload.py:23 · References a credential file in the home directory
- `src/mixcloud_mcp_server/tools/upload.py:34` · References a credential file in the home directory — src/mixcloud_mcp_server/tools/upload.py:34 · References a credential file in the home directory

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