
gnomancer
Your DNA, decoded on your own machine.
gnomancer.com ·
get your raw data ·
install ·
PyPI ·
MCP Registry ·
Discord
Take the raw file you already downloaded from AncestryDNA, 23andMe, MyHeritage, FamilyTreeDNA or LivingDNA and turn it into one readable report. Everything runs on your computer. Nothing is uploaded.
Quick start
pipx install gnomancer # Python 3.10+; Java 11+ for the haplogroup and PharmCAT steps
gnomancer setup # fetches the open-source tools and reference files once (~250 MB)
gnomancer ~/Downloads/AncestryDNA.zip
Open AncestryDNA_analysis/REPORT.html. No Python? curl -fsSL https://gnomancer.com/install.sh | bash does it all. Windows: via WSL.
What you get
- Plain language first. An at-a-glance digest, then a narrative your own AI assistant can write from a prompt the run gives you.
- Lineages. Y haplogroup (yhaplo, plus Yleaf on current YFull/FTDNA/ISOGG trees) and mtDNA haplogroup (Haplogrep3), each with population context.
- Traits and ancestry markers. About 110 well-replicated sites: pigmentation, lactose, caffeine, bitter taste, blood group and more.
- Health, carefully. Carrier sites, common risk variants, a ClinVar scan of every typed site with plausibility scoring, and PharmCAT pharmacogenomics. All collapsed by default so nobody sees a result they didn't ask for.
- Stays current.
gnomancer watchre-checks ClinVar each month and tells you only what was reclassified at sites you carry. - Honest limits. Every section says what the chip can and cannot tell you.
Use it from your AI assistant
gnomancer is also an MCP server. Connect it and ask "what does my report say about caffeine?"
claude mcp add gnomancer -- uvx gnomancer serve # Claude Code; Claude Desktop/Cursor: command "uvx", args ["gnomancer","serve"]
Only derived results reach the assistant, never the raw file. Health tables are separate tools fetched only on request. The repo also works as a Claude plugin (skills/gnomancer/SKILL.md).
Privacy
Your genotype file never leaves your machine. The only network traffic is the one-time download of public tools and references. The optional --ai flag sends the structured results (not the file) to the Anthropic API to write the narrative, and only when you ask.
Not medical advice
A genotyping array reads about 0.02% of the genome at pre-chosen sites, and its calls at rare sites are wrong often enough that a clinical lab found 40% did not confirm. gnomancer tells you what the chip says and how far to trust it. Confirm anything that matters with a clinical-grade test and a clinician or genetic counselor.
More
Discord community · CLI options · vendors and quirks · the marker panel · tools under the hood · development · MCP registry · contributing
MIT licensed. The bundled tools keep their own licenses.
mcp-name: com.gnomancer/gnomancer
Metadata
Release files for gnomancer 0.4.0
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.4.0.tar.gz | 70.5 kB | With provenance | Details for gnomancer-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gnomancer-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for gnomancer-0.4.0-py3-none-any.whl |
Total release size: 141.9 kB
Release files / gnomancer-0.4.0.tar.gz
| Download URL | gnomancer-0.4.0.tar.gz |
|---|---|
| Size | 70.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f5b894d56d8e62e0dc1a3d31625ba7b40f61f3784ffbd96366ba9ca3694f516
|
|
BLAKE2b-256 checksum How to use checksums |
e2764a68c0d6c46d63e981586e0a60a7ae712db61e367418dc1cf853215cbd08
|
| 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.4.0-py3-none-any.whl
| Download URL | gnomancer-0.4.0-py3-none-any.whl |
|---|---|
| Size | 71.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
57656c4c8f2a8d353efa9b4a5a89c9f2691bef70c0e3f1e8dfe3d0570188fc93
|
|
BLAKE2b-256 checksum How to use checksums |
ef4f97d9116dd8a4ab69cd236ec02846580db9148ff6e4b5973bc75031e4657f
|
| 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.4.0
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.4.0.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.