gnomancer@0.5.2
CAUTION· not startedPublisher claims: "Analyzes a consumer raw DNA file (AncestryDNA, 23andMe, MyHeritage, FTDNA, LivingDNA, VCF) entirely on the user's machine: Y and mtDNA haplogroups, traits, ClinVar scan, PharmCAT pharmacogenomics, and a plain-language report. Tools: analyze, summary, section, lookup, narrative_prompt/set_narrative, clinvar_findings, pharmacogenomics. Nothing is uploaded." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- gnomancer.com (its own)Also nih.gov, discord.gg, isogg.org, yfull.com, familytreedna.com, phylotree.org, i-med.ac.at, sitemaps.org, astral.sh, python.org — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable and talks to gnomancer.com, its own; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Pipe-to-shell pattern. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 3 scenarios · 0 deviationsStatic findings
(or `curl -fsSL https://gnomancer.com/install.sh | bash`; Windows needs WSL, see https://gnomancer.com/install/).Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.run([py, "-c", code, str(inp)], capture_output=True, text=True, timeout=1800)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run([str(venv / "bin" / "pip"), "install", "-q", "snps>=2.12", EZANCESTRY_SRC, YLEAF_SRC], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.(or `curl -fsSL https://gnomancer.com/install.sh | bash`; Windows needs WSL, see https://gnomancer.com/install/).Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(cmd + args, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.(d / "summary.json").write_text(json.dumps(dict(input=str(d / "nofile.txt"), args=[], glance={"who": ["Y: R-M269"]}, source="AncestryDNA",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.p = subprocess.run([exe, "-i", str(genos), "-o", str(ydir), "--haplogroup_paths", "--der_snps_detail",Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run([uv, "pip", "install", "-q", "--python", sys.executable, spec], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.run([exe, "classify", "--tree", tree, "--in", str(hsd), "--out", str(out), "--extend-report"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run([sys.executable, "-m", "pip", "install", "-q", spec], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.run([f"{env.get('JAVA_HOME', '')}/bin/java" if env.get("JAVA_HOME") else "java", "-jar", str(JAR),Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.server = MCPServer("gnomancer", version=__version__, instructions=INSTRUCTIONS, website_url="https://gnomancer.com")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.r = subprocess.run([sys.executable, "-m", "gnomancer", "family", *kits, "--names", "dad,mom,child1,stranger", "--out", str(tmp_path / "out"), "--no-haplogroups"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run([sys.executable, str(ROOT / "examples" / "make_family.py"), str(tmp_path / "fam")], check=True, capture_output=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run([sys.executable, str(ROOT / "examples" / "make_demo.py"), str(d)], check=True, capture_output=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run([py311, "-m", "venv", str(venv)], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.run([exe, "-plink", str(ydir / f"{sample}.ped"), "-rg", "hg19", "-o", str(ydir / "out"), "-tree", *TREES,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim codebase: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.