gnomancer
A private, local deep dive into your raw DNA file. One command turns an AncestryDNA, 23andMe, MyHeritage, FamilyTreeDNA, LivingDNA or VCF export into a readable HTML report: file quality, Y and mitochondrial lineages, traits, carrier sites and pharmacogenomics, each with plain-language context and honest limits.
Nothing is uploaded. The only network traffic is the one-time download of public tools and reference files.
pipx install gnomancer # or: pip install gnomancer (Python 3.10+; Java 11+ for haplogroups and PharmCAT)
gnomancer setup # downloads the open-source tools and reference files once (~250 MB) into ~/.gnomancer
gnomancer ~/Downloads/AncestryDNA.zip
open AncestryDNA_analysis/REPORT.html
No Python yet? curl -fsSL https://gnomancer.com/install.sh | bash does all of it on macOS/Linux/WSL.
Not sure how to get the file? gnomancer.com/get-your-data has the steps for every vendor. Full install notes, including Windows: gnomancer.com/install.
Use it from your AI assistant. gnomancer is also an MCP server, so Claude Desktop, Claude Code, Cursor and others can run it and answer questions about your report, all locally:
claude mcp add gnomancer -- ~/gnomancer/.venv/bin/gnomancer serve # Claude Code
Claude Desktop (claude_desktop_config.json):
{ "mcpServers": { "gnomancer": { "command": "/Users/you/gnomancer/.venv/bin/gnomancer", "args": ["serve"] } } }
Tools: analyze, summary, section, lookup, narrative_prompt / set_narrative, and (only on request) clinvar_findings,
pharmacogenomics. The raw file never leaves the machine; only derived results reach the assistant. The repo also doubles
as a Claude plugin (skills/gnomancer/SKILL.md).
What you get
<input>_analysis/
| File | Contents |
|---|---|
REPORT.html |
The report: self-contained, light/dark, printable, searchable marker tables |
REPORT.md |
The same content as Markdown |
summary.json |
Everything machine-readable |
chromosome-qc.tsv, roh.tsv, marker-panel.tsv |
Raw tables |
clinvar-hits.tsv, pharmcat-calls.tsv |
ClinVar and PharmCAT results |
yhaplo/, haplogrep3/, pharmcat/ |
Raw tool outputs |
Report sections:
- In plain language / At a glance – a narrative summary (yours or Claude's) and an automatic digest: who the data says you are, what is worth knowing, what is reassuring, sensible next steps
- Overview – vendor, build, sex, lineages, blood group, quality flags
- Quality – no-call rate, heterozygosity per chromosome, independent sex inference, contamination flags
- Runs of homozygosity – parental relatedness and founder-population signal
- Lineages – Y haplogroup via yhaplo with a second opinion from Yleaf on current YFull/FTDNA/ISOGG trees; mtDNA via Haplogrep3; each with population context
- Multi-site readings – ABO blood group, lactase persistence, TAS2R38 taster haplotype, APOE (collapsed by default)
- Marker panel – ~110 curated sites: ancestry-informative, traits, health, carrier, pharmacogenomics
- ClinVar scan – every typed site checked against ClinVar; pathogenic alleles listed with a plausibility score (strand-ambiguous and homozygous-rare calls are flagged as probable array artifacts)
- PharmCAT – star-allele diplotypes and CPIC phenotypes for 18 pharmacogenes via PharmCAT, with per-gene coverage so you can see how much of each gene the chip actually typed
- Ancestry estimate (
--ancestry) – 1000 Genomes population classification via ezancestry - Limits – what a genotyping array cannot tell you
Health and carrier sections are collapsed by default so that people who would rather not see, say, their APOE genotype are not shown it by accident.
Vendors and quirks
Parsing is delegated to snps, which detects the vendor from the header and
normalizes everything. Quirks that are handled:
| Vendor | Quirk | Handling |
|---|---|---|
| AncestryDNA | CRLF line endings; chromosomes coded 23=X, 24=Y, 25=PAR, 26=MT; two allele columns; no-call 0; indels I/D; diploid-looking GG on Y and MT |
normalized to X/Y/PAR/MT, haploid single letters, NaN no-calls |
| AncestryDNA | V1 (~700k sites, 2012–2016) and V2 (~665k, 2016+) type different sites | report marks not on array per site |
| 23andMe | single genotype column; -- no-call; haploid A; internal i3000001 IDs; v3/v4/v5 chips differ (v5 dropped many PGx sites) |
handled; missing sites reported |
| MyHeritage, FamilyTreeDNA | quoted CSV RSID,CHROMOSOME,POSITION,RESULT |
handled |
| FamilyTreeDNA (old) | build 36 exports | remapped to 37; mtDNA call skipped (build 36 MT is not rCRS) |
| LivingDNA, Genes for Good, tellmeGen, Circle | tab/CSV variants | handled |
| Build 38 exports, VCF | remapped to GRCh37 (chain file downloaded once) | |
| Any | occasional probes reported on the reverse strand | panel auto-flips unambiguous SNPs and flags A/T and C/G ones |
| Any | MT numbering is rCRS (NC_012920) on builds 37/38 | diffed against the bundled rCRS |
The marker panel
gnomancer/data/markers.tsv is a plain TSV anyone can extend:
rsid category gene label ref effect interp0 interp1 interp2 note
ref/effect are the two alleles on the GRCh37 forward strand. effect is the allele that gets counted and
interp0/1/2 is shown for 0/1/2 copies. Categories: ancestry, trait, health, carrier, pgx.
See CONTRIBUTING.md for the sourcing rules.
Haplogroup context lives in gnomancer/data/haplogroup_context.tsv, matched by prefix so a call like R-M269 / R1b1a2a1a2
shows the chain R → R1b → R-M269.
MCP server
gnomancer serve speaks MCP over stdio. Registry manifest: server.json; publishing steps: docs/mcp-registry.md.
Options
gnomancer FILE [--out DIR] [--markers TSV] [--no-y] [--no-yleaf] [--no-mt] [--no-clinvar] [--no-pharmcat] [--ancestry]
[--summary summary.md] [--ai]
Plain-language summary. The report opens with an automatic "at a glance" block built from the results. For a narrative on
top of that, every run also writes summary-prompt.md: paste it to whatever AI assistant you use (Claude, ChatGPT, a local
model), save the answer as summary.md, and re-run with --summary summary.md. Or pass --ai to have Claude write it
directly (pip install anthropic, credentials via ANTHROPIC_API_KEY or ant auth login). --ai is the one path that sends
anything off your machine: the structured results in summary-prompt.md, never the raw genotype file.
--ancestry runs ezancestry for a 1000 Genomes population classification.
ezancestry and Yleaf need Python ≤3.11; setup.sh builds a side venv (.venv-ancestry) for both automatically when
python3.11 is on the PATH, and the CLI uses it when present. First runs download reference data (ezancestry models;
Yleaf's hg19 reference, ~900 MB).
Tools used under the hood
| Tool | What it contributes | Source |
|---|---|---|
snps |
vendor detection, normalization, build remapping | github.com/apriha/snps |
| yhaplo | Y haplogroup (ISOGG 2016 tree) | github.com/23andMe/yhaplo |
| Haplogrep3 + PhyloTree 17 | mtDNA haplogroup | github.com/genepi/haplogrep3 |
| ClinVar | clinically classified variants at every typed site | ncbi.nlm.nih.gov/clinvar |
| PharmCAT | CPIC/PharmGKB star-allele calling | github.com/PharmGKB/PharmCAT |
| ezancestry | 1000 Genomes population classification | github.com/arvkevi/ezancestry |
| Yleaf | second-opinion Y haplogroup on current YFull / FTDNA / ISOGG trees | github.com/genid/Yleaf |
| rCRS (NC_012920.1) | mitochondrial reference | NCBI |
Evaluated and not used (yet): PLINK 2 (nothing an array file needs that is not already here), ADMIXTURE (needs a multi-GB reference panel), pgsc_calc polygenic scores (arrays need imputation first), SNPedia (non-commercial license, no bulk use).
Try it without your own data
.venv/bin/python examples/make_demo.py demo # synthetic AncestryDNA / 23andMe / MyHeritage files
.venv/bin/gnomancer demo/demo_AncestryDNA.txt
Limits, stated plainly
- A genotyping array covers roughly 0.02% of the genome at pre-chosen common sites. It is not a sequence.
- Negative at a site ≠ gene is normal. BRCA1/2, CFTR and similar are covered at a handful of sites only.
- Positive at a rare site is often wrong: 40% of variants from consumer raw data were false positives when a clinical lab re-tested them (Tandy-Connor et al. 2018). The ClinVar section scores each hit for plausibility for this reason.
- CYP2D6 copy number, full HLA typing and rare variants are invisible.
- Y and mtDNA resolution stops at the few thousand / few hundred sites typed.
- Admixture percentages need a reference panel; the vendor's own estimate is the easy source.
- This is not medical advice. Confirm anything that matters with a clinical-grade test and a clinician or genetic counselor.
Website
site/ is the landing page at https://gnomancer.com, served as a Cloudflare Worker with static assets (wrangler.toml).
Deploy with npx wrangler deploy (Node 22+, wrangler login once). It is static: no cookies, no analytics.
Development
./setup.sh # venv, editable install, tools
.venv/bin/pytest
python -m build # sdist + wheel; releases publish to PyPI from GitHub Actions (trusted publishing)
CI runs the tests and builds a demo report on every push. Real raw-data files and *_analysis/ folders are
git-ignored; never commit them.
Related tools
Local: apriha/lineage (shared segments between kits),
PLINK 2, ADMIXTURE + 1000 Genomes, SNPedia.
Web (uploads your data): GEDmatch, James Lick's mthap, Morley's Y-SNP predictor, Promethease, Genetic Genie.
License
MIT. Haplogroup tools and references have their own licenses: yhaplo (23andMe), Haplogrep3 (GENEPI Innsbruck), PhyloTree, ISOGG.
mcp-name: com.gnomancer/gnomancer
Metadata
Release files for gnomancer 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gnomancer-0.3.2.tar.gz | 70.5 kB | With provenance | Details for gnomancer-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gnomancer-0.3.2-py3-none-any.whl | Python 3 | none | any | Details for gnomancer-0.3.2-py3-none-any.whl |
Total release size: 138.7 kB
Release files / gnomancer-0.3.2.tar.gz
| Download URL | gnomancer-0.3.2.tar.gz |
|---|---|
| Size | 70.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08581b91421cc2af6dbca6e7f3509e5af7cc4b28725a13e6c524f1b9c9d65974
|
|
BLAKE2b-256 checksum How to use checksums |
43ab951b428da564f64f02d52cd39e3471fa4fbedab4a4d414d69155fd2f0d0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / gnomancer-0.3.2-py3-none-any.whl
| Download URL | gnomancer-0.3.2-py3-none-any.whl |
|---|---|
| Size | 68.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7fbb52e715320effceb6857283052e4b244649b31becfec1bfbf223921ace440
|
|
BLAKE2b-256 checksum How to use checksums |
7c63514e3ae87a2f0e04ce6fe20b0cb1ce43dcb99c4ea62cb76d4a78fe05e8f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for gnomancer 0.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gnomancer-0.3.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.