gnomancer
PYPI · GNOMANCER
Local raw DNA analysis: haplogroups, traits, ClinVar, pharmacogenomics. Nothing is uploaded.
Available components
Last scanned (20 hours ago)
Scores higher than 78% of PyPI servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 45 of 46 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 45 of 46 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to codebase/gnomancer). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 997 tokens (~83/item across 12 items; 10 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (30% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 +15
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 30 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- Package version: 0.5.0 → 0.5.1 functional
- 2 Nov 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/gnomancer@0.5.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | codebase/gnomancer |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/codebase/gnomancer/.github/workflows/publish.yml@refs/tags/v0.5.1 |
| Rekor log index | 3654714656 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:80b657aa9c637e1ec9c3ad0796e15f3db6b8a97b39e712c6b84285482130f89d |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 45 packages
| Packages resolved | 45 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze ~137
Run gnomancer on a raw DNA file (AncestryDNA, 23andMe, MyHeritage, FamilyTreeDNA, LivingDNA, VCF; .zip OK). Takes one to three minutes; the very first run also downloads ~250 MB of open-source tools and references (a few minutes), automatically. fast=True skips Yleaf, ClinVar and PharmCAT. Returns the output directory, report paths and the at-a-glance digest. The file never leaves this machine.
| Name | Type | Req | Description |
|---|---|---|---|
| ancestry | boolean | – | – |
| fast | boolean | – | – |
| out_dir | – | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
clinvar_findings ~54
ClinVar scan results (pathogenic / likely-pathogenic alleles carried, with plausibility confidence and flags). Health-sensitive: call only when the user asks about disease risk or carrier status.
| Name | Type | Req | Description |
|---|---|---|---|
| report_dir | – | – | – |
No output schema declared.
No examples provided.
clinvar_watch ~84
Re-check ClinVar for this report: downloads a new ClinVar release if NCBI published one, rescans the user's sites and reports only classification changes (newly pathogenic, downgraded, review-status changes). The first run writes a baseline. Health-sensitive: run when the user asks.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| report_dir | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
family ~101
Compare two or more relatives' raw DNA files: shared DNA per pair with a relationship estimate, shared maternal/ paternal lines, side-by-side panel genotypes and, for parent-parent-child sets, which parent each allele came from plus a Mendelian-consistency check. Runs locally. Returns the pair table and report paths.
| Name | Type | Req | Description |
|---|---|---|---|
| haplogroups | boolean | – | – |
| names | – | – | – |
| out_dir | – | – | – |
| paths | array | yes | – |
No output schema declared.
No examples provided.
lookup ~71
Genotype and reading for one rsID. Uses the curated panel when the site is in it; otherwise reads the single site from the user's raw file (nothing else is read or returned). Says so if the chip did not type the site.
| Name | Type | Req | Description |
|---|---|---|---|
| report_dir | – | – | – |
| rsid | string | yes | – |
No output schema declared.
No examples provided.
narrative_prompt ~45
The prompt for writing the plain-language narrative that goes at the top of the report. Follow it exactly, then pass your text to set_narrative.
| Name | Type | Req | Description |
|---|---|---|---|
| report_dir | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pharmacogenomics ~55
PharmCAT star-allele diplotypes and phenotypes per gene, with coverage. Provisional: untyped positions are assumed reference. Call when the user asks about medications or drug metabolism.
| Name | Type | Req | Description |
|---|---|---|---|
| report_dir | – | – | – |
No output schema declared.
No examples provided.
section ~61
Return one section of REPORT.md by (partial, case-insensitive) heading, e.g. 'Paternal', 'Marker panel', 'PharmCAT'. With no name, lists the available section headings.
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | – |
| report_dir | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_narrative ~64
Embed a narrative summary (yours, written from narrative_prompt) at the top of the report. Saves summary.md and regenerates REPORT.html / REPORT.md with the same options as the original run.
| Name | Type | Req | Description |
|---|---|---|---|
| report_dir | – | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
summary ~61
Headline results of the current (or given) report: quality, lineages, ancestry estimate, multi-site readings and the at-a-glance digest. No health tables; use clinvar_findings / pharmacogenomics for those.
| Name | Type | Req | Description |
|---|---|---|---|
| report_dir | – | – | – |
No output schema declared.
No examples provided.
How do I install the gnomancer MCP server?
gnomancer runs locally as a PyPI package, launched with uvx gnomancer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · gnomancer
claude mcp add com-gnomancer-gnomancer -- uvx gnomancer
What is the gnomancer MCP server?
gnomancer is an MCP server listed in the public MCP registry as com.gnomancer/gnomancer. Local raw DNA analysis: haplogroups, traits, ClinVar, pharmacogenomics. Nothing is uploaded. This page covers its PyPI package (gnomancer).
Is the gnomancer MCP server safe to use?
gnomancer scores 79 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the gnomancer MCP server expose?
gnomancer exposes 10 tools: analyze, summary, section, lookup, clinvar_findings, and 5 more. Their descriptions and schemas cost roughly 733 tokens of context every time the server is loaded.
Is the gnomancer MCP server still maintained?
gnomancer is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the gnomancer MCP server under?
gnomancer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.