# Genealogy research toolkit (pypi · genealogy-mcp)

Family history: 171 sources, book search, calendars, kinship, event evidence and research projects

- Trust score: 74/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `genealogy-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/igormel81-genealogy-mcp/genealogy-mcp.md), [page](https://verifymcp.io/servers/igormel81-genealogy-mcp/genealogy-mcp)

## Channel facts

- Registry: `pypi`
- Package: `genealogy-mcp`
- Version: `0.7.0`
- 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-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to igormel81/genealogy-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/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 6855 tokens (~195/item across 35 items; 31 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 33 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).

## Install

### How do I install the Genealogy research toolkit MCP server?

Genealogy research toolkit runs locally as a PyPI package, launched with uvx genealogy-mcp. 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 igormel81-genealogy-mcp -- uvx genealogy-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "igormel81-genealogy-mcp": {
      "command": "uvx",
      "args": [
        "genealogy-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "igormel81-genealogy-mcp": {
      "command": "uvx",
      "args": [
        "genealogy-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add igormel81-genealogy-mcp -- uvx genealogy-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add igormel81-genealogy-mcp --command uvx --arg genealogy-mcp
```

### Hermes

```yaml
mcp_servers:
  igormel81-genealogy-mcp:
    command: "uvx"
    args: ["genealogy-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "igormel81-genealogy-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "genealogy-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add igormel81-genealogy-mcp -t stdio -c uvx -a genealogy-mcp
```

### Other

```json
{
  "mcpServers": {
    "igormel81-genealogy-mcp": {
      "command": "uvx",
      "args": [
        "genealogy-mcp"
      ]
    }
  }
}
```

## 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-05 (score 74, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-04 (score 89, +1)

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

### 2026-11-02 (score 88, +1)

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

### 2026-10-31 (score 87, +1)

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

### 2026-10-29 (score 86, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 70, +1)

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

### 2026-10-24 (score 69, +1)

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

### 2026-10-22 (score 68, +1)

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

## MCP tools (31)

### `find_sources` (~241 tokens)

Find genealogy databases and archives for a country (or region), period and kind of records — 171 sources across
Russia and the former USSR, the Caucasus and Central Asia, Eastern, Western and Northern Europe, Germany, the British
Isles, the Americas, Australia and New Zealand,
each with what it holds and how to search it well.

Input parameters:

- `country` (string): Country or region: 'Ukraine', 'UA', 'Россия', 'europe', 'latin_america', 'russian_empire'; several separated by commas. Empty = any.
- `include_worldwide` (boolean)
- `lang` (string)
- `limit` (integer)
- `records`: Kinds of records: church, vital, census, revision, confession, household, military, repression, deportation, holocaust, forced_labour, displaced, emigration, newspapers, directories, books, graves, t…
- `text` (string): Free text to match in names and descriptions
- `year_from`: First year of interest
- `year_to`: Last year of interest

### `source_details` (~44 tokens)

Everything about one source from the catalogue (by id from find_sources): coverage, access, search tips.

Input parameters:

- `lang` (string)
- `source_id` (string, required)

Output parameters:

- `result` (string)

### `search_links` (~121 tokens)

Ready search links (open them in a browser) in the sources that take a search URL — FamilySearch, Internet Archive
full text, Find a Grave, Arolsen, Geneteka, Open List and others — for a name, with the name's variants.

Input parameters:

- `country` (string)
- `given` (string)
- `place` (string)
- `surname` (string)
- `variants` (boolean): Also make links for the main spelling variants of the surname
- `year_from`
- `year_to`

### `where_are_records` (~333 tokens)

Which archives now hold the records (parish registers, revision lists, confession lists, civil records) of a
province of the Russian Empire, the Kingdom of Poland, Galicia, Bukovina, East Prussia, the Baltics or the Caucasus —
borders moved, so this is often not the archive of today's region. Also works from a modern region back to the
historical provinces it was part of. With a year, says whose land it was then (southern Bessarabia — Cahul, Ismail,
Bolgrad — was Moldavian/Romanian in 1857–1878, all Bessarabia Romanian in 1918–1940 and 1941–1944); with a village,
which church kept its books (a village without a church was recorded in a neighbouring one).

Input parameters:

- `lang` (string)
- `place` (string, required): A historical province or a modern region: «Тульская губерния», 'Volhynia', 'Бессарабия', 'Galicia', «Брянская область», 'Kyiv'; for southern Bessarabia also a district: 'Cahul', «Измаильский уезд», '…
- `village` (string): The village: tells which church kept its registers, where that is known, and how to find out
- `year`: The year of the record: where borders moved (southern Bessarabia 1857–1878, Bessarabia 1918–1944) it decides the country, county and archive

### `search_online` (~265 tokens)

Search an open database live and get the matching records back (title, date, place, link, snippet).
Sends the query to that one site only. Run it for each name form from name_variants; for FamilySearch, Geneteka,
Find a Grave and other sites without an open API use search_links.

Input parameters:

- `given` (string)
- `limit` (integer)
- `place` (string)
- `query` (string): Free text instead of the name fields (e.g. a phrase for the full-text search)
- `source` (string, required): gallica: Gallica — OCR document search (BnF); search_book_pages gives page excerpts; internet_archive: Internet Archive — full text of digitised books, worldwide; chronicling_america: Chronicling Ame…
- `start` (integer): Gallica only: one-based record offset; other providers require 1
- `surname` (string)
- `year_from`
- `year_to`

### `search_book_pages` (~120 tokens)

Find OCR excerpts inside one Gallica book using its ARK/document_id from search_online source='gallica'.
Returns scan sequence numbers and stable page URLs, not verified facts or printed page numbers.
Sends the query only to Gallica's documented ContentSearch API. start is a zero-based result offset.
Access errors are incomplete checks, never no hits; no OCR hit does not prove absence from the scans.

Input parameters:

- `document_id` (string, required)
- `limit` (integer)
- `query` (string, required)
- `start` (integer)

### `place_history` (~109 tokens)

Look a place up in Wikidata: what administrative units it was part of (with years where known), coordinates and the
Wikipedia article — a first step to the uezd, province and parish of a village — and the church its books were kept
in, where that attachment is known. Sends the name to Wikidata.

Input parameters:

- `lang` (string)
- `name` (string, required): A village, town or district, as precise as possible: «Сынково Тульская область»

### `plan_research` (~104 tokens)

A step-by-step research plan for a country and period: which records exist, which guides to read and which
sources to search, in order (free and country-specific first).

Input parameters:

- `country` (string)
- `lang` (string)
- `lead_id` (string)
- `project` (string)
- `question` (string): What we want to find out, with what is known
- `year_from`
- `year_to`

### `film_reading_plan` (~276 tokens)

A plan for reading unindexed FamilySearch films page by page for a parish, years and parts: which films to read
in which order, thumbnails to find the book (title pages, end-of-year summaries naming the church) and full frames
only for the record pages, a rough request budget split into sessions under the site's variable rate limit (pause at
least an hour after HTTP 429, no parallel sessions), and what to log with project_coverage.

Input parameters:

- `films`: Films from the FamilySearch Catalog entry: [{film (DGS number), years ('1860-1875'), frames (images on the film, if shown), item, note}]; empty = how to find them
- `lang` (string)
- `order` (string)
- `parish` (string, required): The church whose books to read, with its village: «Покровская церковь с. Сынково», 'church of Leca'
- `parts`: Parts to read: births, marriages, deaths, confession, revision, census, other; default births, marriages, deaths
- `project` (string): A project (name, site folder or .ged path) whose coverage marks what is already read; it is skipped
- `year_from` (integer, required)
- `year_to`

### `name_variants` (~305 tokens)

All the forms a name can take in records (and its Daitch–Mokotoff Soundex codes): spelling variants, pre-1918 orthography, male/female surname forms
(Колодин/Колодина, Kowalski/Kowalska, Kazlauskas/Kazlauskienė), transliterations (passport, BGN, German, French,
Polish, Romanian, Spanish, Ukrainian, scholarly) and given-name equivalents across languages (Иван = Іоаннъ = Jan = Johann = Juan).
Moldovan and Bessarabian surnames: Romanian and Russian renderings (Călugăreanu = Калугарян = Калугаряну = Кэлугэряну,
Pleș = Плешъ = Плешу), a second surname flagged («Мокану, он же Плеш»), clerk and recognition distortions as hints,
and look-alikes that are another family.

Input parameters:

- `kind` (string): What the name is
- `name` (string, required): The name as found; for a surname also a pair from a register: «Мокану, он же Плеш», 'Mocanu zis Pleș'
- `origin` (string): moldovan: a surname from Moldova, Bessarabia or Romania (found by itself for Romanian letters and endings like -eanu, -escu, -ян, -яну)

### `normalize_date` (~92 tokens)

A date as people write it ('около 1899', 'between 1900 and 1905', '9 de octubre de 1899', '9.10.1899') →
ISO or GEDCOM ('ABT 1899', 'BET 1900 AND 1905', '9 OCT 1899', '1899-10-09').

Input parameters:

- `text` (string, required)

### `convert_calendar` (~186 tokens)

Convert between calendars of old records: Julian (old style; Russia until February 1918: +10 days in the 1600s,
\+11 in the 1700s, +12 in the 1800s, +13 in 1900–1918), Gregorian, Hebrew (Jewish registers, tombstones) and the
French Republican calendar (1792–1805).

Input parameters:

- `date` (string, required): '1899-10-09' / '9.10.1899' (Julian or Gregorian), '15 Nisan 5650' (Hebrew), '18 Brumaire an VIII' (French Republican)
- `from_calendar` (string): The calendar of `date`; auto: Hebrew and Republican are recognised by month names, a plain date is Julian when converting to Gregorian and vice versa
- `to` (string)

### `feast_date` (~132 tokens)

The date of a church feast or fast in a given year (Julian and Gregorian), including movable feasts counted from
Easter. Records and family stories often date events by feasts: «родился на Покров», «венчались после Петрова поста».

Input parameters:

- `church` (string)
- `feast` (string, required): A feast or fast as a record names it: «Покров», «Петров день», «Троица», «Пасха», «Филиппов пост», 'Michaelmas', 'Wielkanoc'…
- `year` (integer, required)

### `cyrillic_numerals` (~117 tokens)

Church Slavonic numerals in old registers and church books: ҂аѡ҃п = 1880, ѳі = 19 (11–19 are written units
first). Reads letters, writes a number, or finds every numeral marked with a titlo in a text.

Input parameters:

- `value` (string, required): Letters to read ('҂аѡ҃п', 'ѳі') or a number to write (1880), or a transcription to scan for numerals

### `dna_match` (~103 tokens)

Which relationships a DNA match fits, from the amount of shared DNA (Shared cM Project 4.0 ranges), closest first.
Several always fit: use documents (and the kinship tool) to decide.

Input parameters:

- `lang` (string)
- `shared_cm` (number, required): Total shared autosomal DNA in centimorgans (cM), as AncestryDNA, MyHeritage, 23andMe, FTDNA or GEDmatch report it

### `birth_year_from_age` (~60 tokens)

The birth-year range implied by an age in a record (census, confession list, death record), exact and loose.

Input parameters:

- `age` (number, required)
- `record_date` (string, required): Date or year of the record that gives the age

### `estimate_birth_year` (~277 tokens)

A birth year estimated from relatives (eldest child −27, spouse and siblings ±8, parents +18…+45, first marriage
at about 22) and ages in records: a GEDCOM date (BET … AND … or ABT …), the most likely year and a ready explanation
to save with it. Also checks the ages against each other: 7 in 1850 and 22 in 1882 cannot be one person — likely two
namesakes.

Input parameters:

- `ages`: Ages in records: [{age, date (or year), source}] — also checked against each other
- `eldest_child_birth`: Year of birth of the eldest known child (the person was about 27, 18–45)
- `father_birth`: Father's year of birth (the person born 18–45 years later)
- `first_marriage`: Year of the person's first marriage (about 22, 16–35)
- `lang` (string)
- `mother_birth`: Mother's year of birth (the person born 18–45 years later)
- `sex` (string)
- `siblings_births`: Brothers' and sisters' years of birth (±8 each)
- `spouse_birth`: Spouse's year of birth (±8; husbands usually a few years older)

### `kinship` (~137 tokens)

What B is to A, named in Russian, English and Romanian (троюродный брат / second cousin / văr de gradul 2,
двоюродный дед / great-uncle), with the expected share of DNA.

Input parameters:

- `down`: …and from the common ancestor down to B
- `half` (boolean)
- `path` (string): Steps from person A: 'father brother son', "mother's sister's daughter", «сын брата отца», «отец матери»
- `sex` (string)
- `up`: Or: generations from A up to the common ancestor

### `check_match` (~142 tokens)

Is the person in a found record ours? Compares fact by fact (with name variants and Julian/rounded-age tolerance)
and gives a verdict: confirmed (2+ independent facts beyond the name), probable, insufficient, conflict or different_person.

Input parameters:

- `found` (object, required): The same fields from the found record
- `known` (object, required): What we know about our person: given, surname, patronymic, father_given, mother_given, mother_surname, spouse_given, spouse_surname, birth_year, birth_place, residence, death_year, children (list), o…
- `lang` (string)
- `year_tolerance` (integer)

### `parent_hypothesis` (~257 tokens)

A working hypothesis about a parent from a patronymic: the father's given name it implies (Петрович → Пётр,
Ильич → Илья), each candidate ranked by name, surname, village and age with the arguments for and against (a
grandson named after him, godparents and sureties of his surname, his household listing a child of this name), a
warning for a namesake from another village, and the record that would settle it. Always a hypothesis — save it as
an open lead or 'probably', never as a link in the tree.

Input parameters:

- `candidates`: Possible fathers found in the records: given, surname, birth_year, death_year, place, sex, children (names listed in the candidate's household), id; empty = how to find them
- `child` (object, required): The person whose parent we look for: given, surname, patronymic (or father_given as recorded), birth_year, place (village), children_given (the person's own children — a son may carry the grandfather…
- `lang` (string)

### `audit_tree` (~177 tokens)

Audit a family tree from any program (GEDCOM) for impossible facts (born after the mother's death, a parent under
14, death before birth), possible duplicates and gaps (no sources, no dates, people cut off from the tree) — a to-do
list for the next search.

Input parameters:

- `codes`: Only these checks: death_before_birth, born_after_mother_death, born_after_father_death, parent_young, parent_old, married_young, long_life, possible_duplicate, bad_date, unconnected, no_documents, e…
- `file` (string, required): Path to a GEDCOM (.ged) or family_tree.json file, or the GEDCOM text itself
- `lang` (string)
- `limit` (integer)

### `draft_archive_request` (~318 tokens)

A draft letter to a registry office or an archive (Russian ZAGS, state, military and FSB archives; any archive in
English, Spanish or Portuguese), with what to attach. Gaps are left in [brackets]. The user sends it — not the tool.

Input parameters:

- `archive` (string): Name and address of the archive
- `birth_place` (string)
- `born` (string)
- `death_place` (string)
- `details` (string)
- `died` (string)
- `kind` (string, required): zags: Registry office (ZAGS): a copy of a birth/marriage/death record; state_archive: State (regional) archive: genealogical search in parish registers, revision lists, etc.; military: Military archi…
- `parents` (string)
- `person` (string)
- `place` (string)
- `project` (string)
- `relation` (string): Who the requester is to the person
- `requester` (string)
- `requester_address` (string)
- `spouse` (string)
- `what` (string): What is requested
- `years` (string)

### `record_guide` (~164 tokens)

How to read and find a kind of record: parish registers, confession lists, revision lists, household books,
WWI and WWII records, repression files, passenger lists, censuses, European civil registration, Latin America,
evaluating evidence — in English, Russian, Ukrainian, and partly Spanish, Portuguese, Polish, German. Without a
topic — the list.

Input parameters:

- `lang` (string): en, ru and uk: every guide; es, pt, pl, de: the guides most used in those countries (others fall back to English)
- `topic` (string): One of: metric_book, confession_list, revision_list, household_book, wwi, wwii, repression, passenger_list, census, civil_registration_europe, latin_america, evidence

Output parameters:

- `result` (string)

### `glossary` (~80 tokens)

Old Russian terms from records — estates, kinship by marriage (шурин, деверь, золовка), archive citation (фонд,
опись, дело, лист), administrative units, pre-1918 letters — explained.

Input parameters:

- `lang` (string)
- `term` (string): A word from an old document, or empty for all

### `project_view` (~187 tokens)

Read the research project kept between conversations — or a family's gene-archive site folder, or the user's own
tree in a GEDCOM file: summary (people,
open leads, recent searches, problems), one record with its family and sources, a text search, the full search
log, or the tree checks. Start every session on an existing project with what='summary'.

Input parameters:

- `id` (string): Record id for what='record' (I1, F1, S1, L1)
- `lang` (string)
- `project` (string): Project name (one per family or research question), the path of a gene-archive site folder, or the path of a .ged file (the user's own tree); empty = list the projects, site folders and trees
- `query` (string): Text for what='search'
- `what` (string)

### `project_save` (~483 tokens)

Add or change a person, family, source or research lead in the project. Every change of an existing record is
logged with the old and new value, the reason and the documents. Save the source first, then cite its S-id.
In a gene-archive site folder the change goes through `gene apply`: refused if it adds an error, logged, committed
to git under the owner's name, and the site is rebuilt. In a .ged file only the changed lines are rewritten (everything
else in the file stays as it was), a copy is kept, and gedcom_changes shows the lines. Ask the user before writing
into their archive or tree.

Input parameters:

- `delete` (boolean)
- `dry_run` (boolean): Check the change and show it without writing — use it to show the user what will be saved
- `kind` (string, required)
- `project` (string, required): Project name, the path of a gene-archive site folder, or the path of a .ged file
- `reason` (string): Why this was added or changed — kept in the corrections log
- `record` (object, required): Fields. person: given_names, surname, sex (M/F), birth/death/burial {date, place_as_recorded, source_ids, note}, notes, research_status ('confirmed' | 'probable' | 'unlinked_candidate'). family: part…
- `source_ids`: Sources (S…) that prove it

### `project_evidence` (~125 tokens)

Review source references for individual birth/death/burial/residence and marriage events, read-only.
Uses the project root (or root_person_id), follows ancestors up to 10 generations and prioritizes closer ones.
Distinguishes missing/broken references, missing locators and reference presence. A person's general sources do
not prove every event; even a located citation still needs inspection. Does not verify parentage or change data.

Input parameters:

- `generations` (integer)
- `limit` (integer)
- `project` (string, required)
- `root_person_id` (string)

### `project_policy` (~137 tokens)

Configure this project's policy only (dry_run by default; save within the owner's authorization).
Keys: max_active_questions (default 3), allow_archive_requests (default true; drafts only),
allow_living_research (default false), owner_tasks [{id, next, due (ISO date), status}].
Read policy, resources and waiting questions with project_view what='workflow'.
A custom archive folder without site.json stays read-only; its policy is stored under GENEALOGY_MCP_HOME/policies, never in that folder.

Input parameters:

- `changes` (object, required)
- `dry_run` (boolean)
- `project` (string, required)

### `project_log` (~153 tokens)

Write a line in the project's research log, so nobody searches the same place twice. Log negative results. Use source_id/lead_id to track the source checklist; unavailable is not no hits.

Input parameters:

- `action` (string, required): What was searched and where: 'FamilySearch index, Kolodin, Tula 1880–1890'
- `lead_id` (string)
- `outcome` (string)
- `project` (string, required): Project name, the path of a gene-archive site folder, or the path of a .ged file
- `result` (string, required): What came out — 'nothing found' is a result too
- `scope` (string)
- `source_id` (string)

### `project_coverage` (~336 tokens)

What has already been read in the registers: parish → year → part → film and frames → status (complete, partial
up to No. …, not found). Mark each book when you finish it, and ask what is still unread for these villages and
years before opening a film — so nobody reads the same frames twice. Kept with the project (for a .ged file in the
file next to it; for a gene-archive site in a file of this server, read together with the site's own coverage).

Input parameters:

- `action` (string): mark: save what was read; unread: what is still unread for places and years; list: everything recorded
- `dry_run` (boolean): For mark: show the change without writing
- `entries`: For mark: one entry per book read — parish (the church whose book it is), villages (that church's villages in the book), year, part (births, marriages, deaths, confession, revision, census, other), f…
- `lang` (string)
- `parts`: For unread: the parts to check; default births, marriages, deaths
- `places`: For unread/list: parishes or villages (a village is matched through the entries that name it)
- `project` (string, required): Project name, the path of a gene-archive site folder, or the path of a .ged file
- `year_from`
- `year_to`

### `project_transfer` (~92 tokens)

Export the project as GEDCOM 5.5.1 (for MyHeritage, Ancestry, Gramps, Geni…) next to the project file, or start a
new project from a GEDCOM exported by another program.

Input parameters:

- `direction` (string, required)
- `file` (string): For import: path to a .ged file or the GEDCOM text
- `project` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 89
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 87
- 2026-10-31: 87
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 68
- 2026-10-22: 68
- 2026-10-21: 67
- 2026-10-20: 67
- 2026-10-19: 66
- 2026-10-18: 66
- 2026-10-17: 81
- 2026-10-16: 65
- 2026-10-15: 80
- 2026-10-14: 64
- 2026-10-13: 49
- 2026-10-12: 49

## Common questions

### What is the Genealogy research toolkit MCP server?

Genealogy research toolkit is an MCP server listed in the public MCP registry as io.github.igormel81/genealogy-mcp. Family history: 171 sources, book search, calendars, kinship, event evidence and research projects. This page covers its PyPI package (genealogy-mcp).

### Is the Genealogy research toolkit MCP server safe to use?

Genealogy research toolkit scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Genealogy research toolkit MCP server expose?

Genealogy research toolkit exposes 31 tools: find_sources, source_details, search_links, where_are_records, search_online, and 26 more. Their descriptions and schemas cost roughly 5,673 tokens of context every time the server is loaded.

### Is the Genealogy research toolkit MCP server still maintained?

Genealogy research toolkit is still listed as active in the MCP registry. We last reached this channel on 5 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 Genealogy research toolkit MCP server under?

Genealogy research toolkit 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/genealogy-mcp/
- Socket report: https://socket.dev/pypi/package/genealogy-mcp
- Repository: https://github.com/igormel81/genealogy-mcp
- Changelog RSS feed: https://verifymcp.io/servers/igormel81-genealogy-mcp/genealogy-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/igormel81-genealogy-mcp/genealogy-mcp.json
- HTML version of this page: https://verifymcp.io/servers/igormel81-genealogy-mcp/genealogy-mcp