Propose a patch

Evidence

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

diff --git a/nextcloud_mcp_server/auth/oauth_routes.py b/nextcloud_mcp_server/auth/oauth_routes.py
--- a/nextcloud_mcp_server/auth/oauth_routes.py
+++ b/nextcloud_mcp_server/auth/oauth_routes.py
@@ -867,1 +867,0 @@
-f"AS proxy token exchange failed: {response.status_code} {response.text}"
@@ -962,1 +961,0 @@
-"AS proxy token: received code=%s client_id=%s redirect_uri=%s "
@@ -971,1 +969,0 @@
-logger.warning("AS proxy token: Missing 'code' parameter")
@@ -981,1 +978,0 @@
-"AS proxy token: Invalid or expired code (active_codes=%d)",
@@ -994,1 +990,0 @@
-logger.warning("AS proxy token: Proxy code expired (age=%.1fs, TTL=60s)", age)

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.65.6. 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: nextcloud-mcp-server-tai040502: Credential pass-through configuration (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/pypi/nextcloud-mcp-server-tai040502/0.65.6

## Findings with a location
- `nextcloud_mcp_server/auth/oauth_routes.py:962` · Credential pass-through configuration — nextcloud_mcp_server/auth/oauth_routes.py:962 · Credential pass-through configuration — agent relays sensitive credentials
- `nextcloud_mcp_server/auth/oauth_routes.py:994` · Credential pass-through configuration — nextcloud_mcp_server/auth/oauth_routes.py:994 · Credential pass-through configuration — agent relays sensitive credentials
- `nextcloud_mcp_server/auth/oauth_routes.py:867` · Credential pass-through configuration — nextcloud_mcp_server/auth/oauth_routes.py:867 · Credential pass-through configuration — agent relays sensitive credentials
- `nextcloud_mcp_server/auth/oauth_routes.py:981` · Credential pass-through configuration — nextcloud_mcp_server/auth/oauth_routes.py:981 · Credential pass-through configuration — agent relays sensitive credentials
- `nextcloud_mcp_server/auth/oauth_routes.py:971` · Credential pass-through configuration — nextcloud_mcp_server/auth/oauth_routes.py:971 · Credential pass-through configuration — agent relays sensitive credentials

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