Propose a patch

Evidence

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

diff --git a/src/orcaslicer_mcp/data/print_settings_schema.json b/src/orcaslicer_mcp/data/print_settings_schema.json
--- a/src/orcaslicer_mcp/data/print_settings_schema.json
+++ b/src/orcaslicer_mcp/data/print_settings_schema.json
@@ -9529,1 +9529,0 @@
-…sed by putting the user name and password into the URL in the following format: https://username:password@your-octopi-address/", "unit": null, "type": "coString", "min": null, "m…
diff --git a/src/orcaslicer_mcp/guard.py b/src/orcaslicer_mcp/guard.py
--- a/src/orcaslicer_mcp/guard.py
+++ b/src/orcaslicer_mcp/guard.py
@@ -79,1 +79,0 @@
-# URL (the print_host tooltip documents https://user:password@host/). The host itself, the
diff --git a/src/orcaslicer_mcp/printer/target.py b/src/orcaslicer_mcp/printer/target.py
--- a/src/orcaslicer_mcp/printer/target.py
+++ b/src/orcaslicer_mcp/printer/target.py
@@ -249,1 +249,0 @@
-# percent-encoded: urllib would drop or misread the rest, e.g. 'http://user:123?x@host'.

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

## 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 73/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/orcaslicer-mcp/0.1.25

## Findings with a location
- `src/orcaslicer_mcp/data/print_settings_schema.json:9529` · URL with embedded credentials — src/orcaslicer_mcp/data/print_settings_schema.json:9529 · URL with embedded credentials — may be phishing or credential leaking
- `src/orcaslicer_mcp/guard.py:79` · URL with embedded credentials — src/orcaslicer_mcp/guard.py:79 · URL with embedded credentials — may be phishing or credential leaking
- `src/orcaslicer_mcp/printer/target.py:249` · URL with embedded credentials — src/orcaslicer_mcp/printer/target.py:249 · URL with embedded credentials — may be phishing or credential leaking

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