Propose a patch

Evidence

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

diff --git a/tests/test_core.py b/tests/test_core.py
--- a/tests/test_core.py
+++ b/tests/test_core.py
@@ -334,1 +334,0 @@
-"-ihttps://user:token@example/simple",
@@ -342,1 +341,0 @@
-args = ("--index-url=https://user:token@example/simple", "example-mcp")
@@ -413,1 +411,0 @@
-"https://user:s3cret@example/simple",
@@ -416,1 +413,0 @@
-"https://user:pa/ss@example/simple",
@@ -417,1 +413,0 @@
-"https://user:p@ss@example/simple",
diff --git a/tests/test_bootstrap.py b/tests/test_bootstrap.py
--- a/tests/test_bootstrap.py
+++ b/tests/test_bootstrap.py
@@ -737,1 +737,0 @@
-"print('https://user:[email protected] token=abc', file=sys.stderr); "
@@ -755,1 +754,0 @@
-spec = _spec(install_args=("--index-url=https://user:s3cret@example/simple", "example-mcp"))

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.0. 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: python-mcp-bootstrap: URL with embedded credentials (KillerSkills verdict caution 78)

## 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 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/pypi/python-mcp-bootstrap/0.2.0

## Findings with a location
- `tests/test_core.py:417` · URL with embedded credentials — tests/test_core.py:417 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_bootstrap.py:755` · URL with embedded credentials — tests/test_bootstrap.py:755 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_core.py:342` · URL with embedded credentials — tests/test_core.py:342 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_core.py:416` · URL with embedded credentials — tests/test_core.py:416 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_bootstrap.py:737` · URL with embedded credentials — tests/test_bootstrap.py:737 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_core.py:334` · URL with embedded credentials — tests/test_core.py:334 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_core.py:413` · URL with embedded credentials — tests/test_core.py:413 · 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._