Propose a patch

Evidence

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

diff --git a/tests/unit/test_github_provider.py b/tests/unit/test_github_provider.py
--- a/tests/unit/test_github_provider.py
+++ b/tests/unit/test_github_provider.py
@@ -69,1 +69,0 @@
-assert "https://x-access-token:[email protected]/test-org/billing-service.git" == auth_url
@@ -120,1 +119,0 @@
-stderr="fatal: Authentication failed for 'https://x-access-token:[email protected]/org/repo.git'",
diff --git a/src/mesh_mcp/providers/github.py b/src/mesh_mcp/providers/github.py
--- a/src/mesh_mcp/providers/github.py
+++ b/src/mesh_mcp/providers/github.py
@@ -226,1 +226,0 @@
-return f"https://x-access-token:{token}@github.com/{owner}/{repo}.git"

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mesh-mcp/0.3.1

## Findings with a location
- `tests/unit/test_github_provider.py:120` · URL with embedded credentials — tests/unit/test_github_provider.py:120 · URL with embedded credentials — may be phishing or credential leaking
- `tests/unit/test_github_provider.py:69` · URL with embedded credentials — tests/unit/test_github_provider.py:69 · URL with embedded credentials — may be phishing or credential leaking
- `src/mesh_mcp/providers/github.py:226` · URL with embedded credentials — src/mesh_mcp/providers/github.py:226 · 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._