# gnomancer (pypi · gnomancer)

Local raw DNA analysis: haplogroups, traits, ClinVar, pharmacogenomics. Nothing is uploaded.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `gnomancer`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-gnomancer-gnomancer/gnomancer.md), [page](https://verifymcp.io/servers/com-gnomancer-gnomancer/gnomancer)

## Channel facts

- Registry: `pypi`
- Package: `gnomancer`
- Version: `0.5.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 45 of 46 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - Dependency health was assessed across the 45 of 46 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to codebase/gnomancer).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 997 tokens (~83/item across 12 items; 10 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (30% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

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

### Claude

```bash
claude mcp add com-gnomancer-gnomancer -- uvx gnomancer
```

### Cursor

```json
{
  "mcpServers": {
    "com-gnomancer-gnomancer": {
      "command": "uvx",
      "args": [
        "gnomancer"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gnomancer-gnomancer": {
      "command": "uvx",
      "args": [
        "gnomancer"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-gnomancer-gnomancer -- uvx gnomancer
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gnomancer-gnomancer": {
      "type": "local",
      "command": [
        "uvx",
        "gnomancer"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gnomancer-gnomancer --command uvx --arg gnomancer
```

### Hermes

```yaml
mcp_servers:
  com-gnomancer-gnomancer:
    command: "uvx"
    args: ["gnomancer"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-gnomancer-gnomancer": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "gnomancer"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gnomancer-gnomancer -t stdio -c uvx -a gnomancer
```

### Other

```json
{
  "mcpServers": {
    "com-gnomancer-gnomancer": {
      "command": "uvx",
      "args": [
        "gnomancer"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 64, +15)

- [security regression] Malware scan: pass → unverified
- [security improvement] 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] 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

### 2026-11-02 (score 49)

First indexed and scored.

## MCP tools (10)

### `analyze` (~137 tokens)

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.

Input parameters:

- `ancestry` (boolean)
- `fast` (boolean)
- `out_dir`
- `path` (string, required)

### `summary` (~61 tokens)

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.

Input parameters:

- `report_dir`

### `section` (~61 tokens)

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.

Input parameters:

- `name`
- `report_dir`

Output parameters:

- `result` (string)

### `lookup` (~71 tokens)

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.

Input parameters:

- `report_dir`
- `rsid` (string, required)

### `clinvar_findings` (~54 tokens)

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.

Input parameters:

- `report_dir`

### `pharmacogenomics` (~55 tokens)

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.

Input parameters:

- `report_dir`

### `clinvar_watch` (~84 tokens)

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.

Input parameters:

- `force` (boolean)
- `report_dir`

Output parameters:

- `result` (string)

### `family` (~101 tokens)

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.

Input parameters:

- `haplogroups` (boolean)
- `names`
- `out_dir`
- `paths` (array, required)

### `narrative_prompt` (~45 tokens)

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.

Input parameters:

- `report_dir`

Output parameters:

- `result` (string)

### `set_narrative` (~64 tokens)

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.

Input parameters:

- `report_dir`
- `text` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-gnomancer-gnomancer/gnomancer#diagnostics

## Score history

- 2026-11-04: 79
- 2026-11-03: 64
- 2026-11-02: 49

## Common questions

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

## Links

- PyPI project: https://pypi.org/project/gnomancer/
- Socket report: https://socket.dev/pypi/package/gnomancer
- Repository: https://github.com/codebase/gnomancer
- Website: https://gnomancer.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-gnomancer-gnomancer/gnomancer.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gnomancer-gnomancer/gnomancer.json
- HTML version of this page: https://verifymcp.io/servers/com-gnomancer-gnomancer/gnomancer