# Zovo Pedigree Charts (remote · gedcom-charts.zovo.one)

Pedigree charts from GEDCOM

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gedcom-charts.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-gedcom-charts/gedcom-charts.md), [page](https://verifymcp.io/servers/theluckystrike-gedcom-charts/gedcom-charts)

## Channel facts

- Endpoint: `https://gedcom-charts.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/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).
  - Context-footprint check failed: tool/resource definitions use about 861 tokens (~287/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Pedigree Charts MCP server?

Zovo Pedigree Charts is a hosted endpoint at https://gedcom-charts.zovo.one/mcp, so there is nothing to install locally. 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 --transport http theluckystrike-gedcom-charts 'https://gedcom-charts.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-gedcom-charts": {
      "url": "https://gedcom-charts.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-gedcom-charts": {
      "type": "http",
      "url": "https://gedcom-charts.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-gedcom-charts]
url = "https://gedcom-charts.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-gedcom-charts": {
      "type": "remote",
      "url": "https://gedcom-charts.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-gedcom-charts --url 'https://gedcom-charts.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-gedcom-charts:
    url: "https://gedcom-charts.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-gedcom-charts": {
      "Transport": "http",
      "Url": "https://gedcom-charts.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-gedcom-charts -t streamable-http -u 'https://gedcom-charts.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-gedcom-charts": {
      "type": "http",
      "url": "https://gedcom-charts.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-19 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 73)

First indexed and scored.

## MCP tools (2)

### `generate_pedigree_chart` (~436 tokens)

Generate pedigree chart from GEDCOM

Use this when the user wants a pedigree chart, an ancestor chart, a printable family tree of someone's ancestors, or "a chart from my GEDCOM file" from a GEDCOM (.ged) file they attached or pasted (exported from Ancestry, FamilySearch, MyHeritage, Gramps, RootsMagic, Family Tree Maker or similar). Pass the attachment as file (or the pasted text as gedcom_text), the person by name or ID, and 4 to 6 generations. Returns a printable landscape PDF with Ahnentafel numbers, dashed blank boxes for unknown ancestors and an ancestor list page, an Excel file of all individuals and families, and data checks (broken links, impossible dates, parents born after their children or under 12, loops). If several people match the name, it lists them with IDs: ask the user which one. Does not research ancestors, add people, or change the file; do not use it for a tree described in words with no GEDCOM file.

Input parameters:

- `file` (object): The GEDCOM file (.ged) exported from a genealogy program or website, e.g. family.ged. A .zip that contains one .ged file also works.
- `gedcom_text` (string|null): Fallback only: GEDCOM text pasted into the chat, starting with lines like "0 HEAD" and "0 @I1@ INDI". Prefer file when the user attached a .ged file.
- `generations` (number|string|null): Generations on the chart including the person, 4 to 6, e.g. 5 (default): person, parents, grandparents, great- and 2x great-grandparents.
- `page_size` (string|null): "Letter" (default) or "A4", printed landscape.
- `person` (string|null): Whose ancestors to chart: a name as written in the file, optionally with a birth year, e.g. "Mary Ellen Walsh 1921", or a GEDCOM ID such as "@I12@". Leave empty to use the person with the most known…

Output parameters:

- `ancestor_slots` (number)
- `ancestors` (array)
- `ancestors_known` (number)
- `ancestors_shown` (object)
- `by_generation` (array)
- `check_counts` (array)
- `checks` (array)
- `checks_shown` (object)
- `checks_total` (number)
- `completeness_percent` (number)
- `continues` (array)
- `continues_total` (number)
- `downloads` (object)
- `file` (object)
- `generations` (number)
- `kind` (string)
- `notes` (array)
- `page_size` (string)
- `pedigree_collapse` (array)
- `person` (object)
- `person_chosen` (string)

### `convert_gedcom_to_excel` (~266 tokens)

Convert GEDCOM to Excel

Use this when the user wants to convert a GEDCOM file to Excel or a spreadsheet, list everyone in their family tree file, or check a GEDCOM (.ged) file for errors ("open my gedcom in excel", "find mistakes in my family tree file"). Pass the attachment as file or pasted text as gedcom_text. Returns an Excel workbook with one row per individual (names, birth and death dates and places, parents, spouse families), one row per family, and a Checks sheet listing broken links, impossible dates, people born after they died or older than 120, parents born after their children or under 12, and people recorded as their own ancestor. Does not change or fix the GEDCOM file, research records, or draw a chart (use generate_pedigree_chart for the chart).

Input parameters:

- `file` (object): The GEDCOM file (.ged) exported from a genealogy program or website, e.g. family.ged. A .zip that contains one .ged file also works.
- `gedcom_text` (string|null): Fallback only: GEDCOM text pasted into the chat, starting with lines like "0 HEAD" and "0 @I1@ INDI". Prefer file when the user attached a .ged file.

Output parameters:

- `check_counts` (array)
- `checks` (array)
- `checks_shown` (object)
- `checks_total` (number)
- `downloads` (object)
- `file` (object)
- `kind` (string)
- `notes` (array)
- `people_preview` (array)
- `people_preview_count` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-gedcom-charts/gedcom-charts#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 75
- 2026-11-11: 75
- 2026-11-10: 74
- 2026-11-09: 74
- 2026-11-08: 73

## Common questions

### What is the Zovo Pedigree Charts MCP server?

Zovo Pedigree Charts is an MCP server listed in the public MCP registry as io.github.theluckystrike/gedcom-charts. Pedigree charts from GEDCOM. This page covers its hosted endpoint (https://gedcom-charts.zovo.one/mcp).

### Is the Zovo Pedigree Charts MCP server safe to use?

Zovo Pedigree Charts scores 79 out of 100 on VerifyMCP. 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 Zovo Pedigree Charts MCP server expose?

Zovo Pedigree Charts exposes 2 tools: generate_pedigree_chart, convert_gedcom_to_excel. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.

### Does the Zovo Pedigree Charts MCP server require authentication?

No. We connected to Zovo Pedigree Charts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Pedigree Charts MCP server still maintained?

Zovo Pedigree Charts is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zovo Pedigree Charts MCP server?

VerifyMCP ran 14 checks on Zovo Pedigree Charts, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://gedcom-charts.zovo.one/mcp
- Website: https://gedcom-charts.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-gedcom-charts/gedcom-charts.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-gedcom-charts/gedcom-charts/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-gedcom-charts/gedcom-charts.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-gedcom-charts/gedcom-charts
