Propose a patch

Evidence

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

diff --git a/tests/fixtures/product-iphone15.html b/tests/fixtures/product-iphone15.html
--- a/tests/fixtures/product-iphone15.html
+++ b/tests/fixtures/product-iphone15.html
@@ -3,1 +3,0 @@
-…gValue":5},"itemReviewed":{"@type":"Product","name":"iPhone 15 128 GB","image":"https://productimages.hepsiburada.net/s/462/424-600/110000498569710.jpg","sku":"HBCV00004X9ZCH","brand":{"@type":"Brand","name":"Apple"}}},{"@type":"Review","author":"Asım K******","dateP…

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

## 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 64/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/hepsiburada-mcp/0.1.0

## Findings with a location
- `tests/fixtures/product-iphone15.html:2` · URL with embedded credentials — tests/fixtures/product-iphone15.html:2 · URL with embedded credentials — may be phishing or credential leaking
- `tests/fixtures/product-iphone15.html:3` · URL with embedded credentials — tests/fixtures/product-iphone15.html:3 · URL with embedded credentials — may be phishing or credential leaking

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