Propose a patch

Evidence

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

diff --git a/src/studylife_mcp/oauth_provider.py b/src/studylife_mcp/oauth_provider.py
--- a/src/studylife_mcp/oauth_provider.py
+++ b/src/studylife_mcp/oauth_provider.py
@@ -190,1 +190,0 @@
-@import url('https://fonts.googleapis.com/css2?family=DM+Sans:ital,opsz,wght@0,9..40,300;0,9..40,400;0,9..40,500;1,9..40,300&display=swap');
diff --git a/docs/decisions.md b/docs/decisions.md
--- a/docs/decisions.md
+++ b/docs/decisions.md
@@ -92,1 +92,0 @@
-- **Why:** CLAUDE.md requires "keine Update-/Delete-Tools... ausgeschlossen, nicht nur unimplementiert" — a fixed, closed set of Python functions already satisfies that; a separate whitelist-checking 

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 63/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/studylife-mcp/1.14.105

## Findings with a location
- `src/studylife_mcp/oauth_provider.py:190` · URL with embedded credentials — src/studylife_mcp/oauth_provider.py:190 · URL with embedded credentials — may be phishing or credential leaking
- `docs/decisions.md:92` · Instructs the agent to modify its persistent memory or instruction files — docs/decisions.md:92 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

## 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._