Propose a patch

Evidence

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

diff --git a/web/tests/smoke.test.mjs b/web/tests/smoke.test.mjs
--- a/web/tests/smoke.test.mjs
+++ b/web/tests/smoke.test.mjs
@@ -47,1 +47,0 @@
-for (const url of ["https://user:[email protected]", "https://example.com?token=x", "https://example.com#x", "http://example.com"]) {
diff --git a/web/src/gedcom-decoding.ts b/web/src/gedcom-decoding.ts
--- a/web/src/gedcom-decoding.ts
+++ b/web/src/gedcom-decoding.ts
@@ -71,1 +71,0 @@
-try { binary = atob(encoded); } catch { throw new HttpError(400, "Invalid GEDCOM file encoding. Choose the file again."); }

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: family-tree-mcp: URL with embedded credentials (KillerSkills verdict caution 68)

## 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 68/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

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

## Findings with a location
- `web/tests/smoke.test.mjs:47` · URL with embedded credentials — web/tests/smoke.test.mjs:47 · URL with embedded credentials — may be phishing or credential leaking
- `web/src/gedcom-decoding.ts:71` · Host or code assembled from base64 fragments — web/src/gedcom-decoding.ts:71 · Host or code assembled from base64 fragments

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