MCP servers › io.github.igormel81 › genealogy-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.igormel81/genealogy-mcp

Family history: 171 sources, book search, calendars, kinship, event evidence and research projects — the publisher's description

7 of 8 record checks metRead-only · tools listed 2026-10-23Topic: data-and-databases · AI-classifiedversion 0.7.0PythonMITstandard input/output31 tools

Summary

io.github.igormel81/genealogy-mcp is a local MCP server listed in the official MCP registry at version 0.7.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 31 tools, 4 resources and 4 prompts.

Record checks

7 of 8 record checks met · 1 does not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 4 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: PyPI · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 31
Described as changing data: 5 of 31 toolsAI-classified
Mainly works on: files and code on the machine it runs onAI-classified
Topic: data-and-databasesAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

5 tools are described as changing something (project_save, project_policy, project_log, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.7.0, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-12 (earliest version still in the registry; older removed versions would be earlier)

Version history

11 versions listed, 2026-10-12 to 2026-10-21; 11 in the 90 days before the 2026-10-23 snapshot.

Most recent 11 versions

0.7.0 · 2026-10-21
0.6.0 · 2026-10-18
0.5.1 · 2026-10-15
0.5.0 · 2026-10-13
0.4.1 · 2026-10-12
0.4.0 · 2026-10-12
0.3.2 · 2026-10-12
0.3.1 · 2026-10-12
0.3.0 · 2026-10-12
0.2.0 · 2026-10-12
0.1.0 · 2026-10-12

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.7.0 (published 2026-10-21).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

31tools

4resources

4prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

5 of 31 tools are described as changing something (creating, editing, deleting, sending or running).

find_sourceson 1 other serverreads or searches
“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 Northe…”
Publisher declares: read-only yes · open-world no
8 inputs
- countrystring“Country or region: 'Ukraine', 'UA', 'Россия', 'europe', 'latin_america', 'russian_empire'; several separated by commas.”
- year_frominteger or null“First year of interest”
- year_tointeger or null“Last year of interest”
- recordsarray or null“Kinds of records: church, vital, census, revision, confession, household, military, repression, deportation, holocaust, forced_labour, displaced, emigration, n…”
- textstring“Free text to match in names and descriptions”
- include_worldwideboolean
- langstring
- limitinteger
source_detailsreads or searches
“Everything about one source from the catalogue (by id from find_sources): coverage, access, search tips.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
- source_idstringrequired
- langstring
search_linkson 2 other serversreads or searches
“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 …”
Publisher declares: read-only yes · open-world no
7 inputs
- surnamestring
- givenstring
- countrystring
- year_frominteger or null
- year_tointeger or null
- placestring
- variantsboolean“Also make links for the main spelling variants of the surname”
where_are_recordsreads or searches
“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, th…”
Publisher declares: read-only yes · open-world no
4 inputs, 1 required
- placestringrequired“A historical province or a modern region: «Тульская губерния», 'Volhynia', 'Бессарабия', 'Galicia', «Брянская область», 'Kyiv'; for southern Bessarabia also a …”
- yearinteger or null“The year of the record: where borders moved (southern Bessarabia 1857–1878, Bessarabia 1918–1944) it decides the country, county and archive”
- villagestring“The village: tells which church kept its registers, where that is known, and how to find out”
- langstring
search_onlinereads or searches
“Search an open database live and get the matching records back (title, date, place, link, snippet).”
Publisher declares: read-only yes · open-world yes
9 inputs, 1 required
- sourcestringrequired“gallica: Gallica — OCR document search (BnF); search_book_pages gives page excerpts; internet_archive: Internet Archive — full text of digitised books, worldwi…”
- surnamestring
- givenstring
- year_frominteger or null
- year_tointeger or null
- placestring
- querystring“Free text instead of the name fields (e.g.”
- startinteger“Gallica only: one-based record offset; other providers require 1”
- limitinteger
search_book_pagesreads or searches
“Find OCR excerpts inside one Gallica book using its ARK/document_id from search_online source='gallica'.”
Publisher declares: read-only yes · open-world yes
4 inputs, 2 required
- document_idstringrequired
- querystringrequired
- startinteger
- limitinteger
place_historyreads or searches
“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 — an…”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- namestringrequired“A village, town or district, as precise as possible: «Сынково Тульская область»”
- langstring
plan_researchgenerates content
“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).”
Publisher declares: read-only yes · open-world no
7 inputs
- countrystring
- year_frominteger or null
- year_tointeger or null
- questionstring“What we want to find out, with what is known”
- langstring
- projectstring
- lead_idstring
film_reading_plangenerates content
“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 …”
Publisher declares: read-only yes · open-world no
8 inputs, 2 required
- parishstringrequired“The church whose books to read, with its village: «Покровская церковь с.”
- year_fromintegerrequired
- year_tointeger or null
- partsarray or null“Parts to read: births, marriages, deaths, confession, revision, census, other; default births, marriages, deaths”
- filmsarray or null“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 t…”
- projectstring“A project (name, site folder or .ged path) whose coverage marks what is already read; it is skipped”
- orderstring
- langstring
name_variantscalculates or converts
“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/K…”
Publisher declares: read-only yes · open-world no
3 inputs, 1 required
- namestringrequired“The name as found; for a surname also a pair from a register: «Мокану, он же Плеш», 'Mocanu zis Pleș'”
- kindstring“What the name is”
- originstring“moldovan: a surname from Moldova, Bessarabia or Romania (found by itself for Romanian letters and endings like -eanu, -escu, -ян, -яну)”
normalize_datecalculates or converts
“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').”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- textstringrequired
convert_calendarcalculates or converts
“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 regist…”
Publisher declares: read-only yes · open-world no
3 inputs, 1 required
- datestringrequired“'1899-10-09' / '9.10.1899' (Julian or Gregorian), '15 Nisan 5650' (Hebrew), '18 Brumaire an VIII' (French Republican)”
- tostring
- from_calendarstring“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”

Show 19 more tools

feast_datecalculates or converts
“The date of a church feast or fast in a given year (Julian and Gregorian), including movable feasts counted from Easter.”
Publisher declares: read-only yes · open-world no
3 inputs, 2 required
- feaststringrequired“A feast or fast as a record names it: «Покров», «Петров день», «Троица», «Пасха», «Филиппов пост», 'Michaelmas', 'Wielkanoc'…”
- yearintegerrequired
- churchstring
cyrillic_numeralscalculates or converts
“Church Slavonic numerals in old registers and church books: ҂аѡ҃п = 1880, ѳі = 19 (11–19 are written units first).”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- valuestringrequired“Letters to read ('҂аѡ҃п', 'ѳі') or a number to write (1880), or a transcription to scan for numerals”
dna_matchcalculates or converts
“Which relationships a DNA match fits, from the amount of shared DNA (Shared cM Project 4.0 ranges), closest first.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
- shared_cmnumberrequired“Total shared autosomal DNA in centimorgans (cM), as AncestryDNA, MyHeritage, 23andMe, FTDNA or GEDmatch report it”
- langstring
birth_year_from_agecalculates or converts
“The birth-year range implied by an age in a record (census, confession list, death record), exact and loose.”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
- agenumberrequired
- record_datestringrequired“Date or year of the record that gives the age”
estimate_birth_yearcalculates or converts
“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 likel…”
Publisher declares: read-only yes · open-world no
9 inputs
- sexstring
- eldest_child_birthstring or null“Year of birth of the eldest known child (the person was about 27, 18–45)”
- spouse_birthstring or null“Spouse's year of birth (±8; husbands usually a few years older)”
- siblings_birthsarray or null“Brothers' and sisters' years of birth (±8 each)”
- father_birthstring or null“Father's year of birth (the person born 18–45 years later)”
- mother_birthstring or null“Mother's year of birth (the person born 18–45 years later)”
- first_marriagestring or null“Year of the person's first marriage (about 22, 16–35)”
- agesarray or null“Ages in records: [{age, date (or year), source}] — also checked against each other”
- langstring
kinshipcalculates or converts
“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.”
Publisher declares: read-only yes · open-world no
5 inputs
- pathstring“Steps from person A: 'father brother son', "mother's sister's daughter", «сын брата отца», «отец матери»”
- upinteger or null“Or: generations from A up to the common ancestor”
- downinteger or null“…and from the common ancestor down to B”
- sexstring
- halfboolean
check_matchcalculates or converts
“Is the person in a found record ours?”
Publisher declares: read-only yes · open-world no
4 inputs, 2 required
- knownobjectrequired“What we know about our person: given, surname, patronymic, father_given, mother_given, mother_surname, spouse_given, spouse_surname, birth_year, birth_place, r…”
- foundobjectrequired“The same fields from the found record”
- year_toleranceinteger
- langstring
parent_hypothesiscalculates or converts
“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 f…”
Publisher declares: read-only yes · open-world no
3 inputs, 1 required
- childobjectrequired“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 ch…”
- candidatesarray or null“Possible fathers found in the records: given, surname, birth_year, death_year, place, sex, children (names listed in the candidate's household), id; empty = ho…”
- langstring
audit_tree
“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 c…”
Publisher declares: read-only yes · open-world no
4 inputs, 1 required
- filestringrequired“Path to a GEDCOM (.ged) or family_tree.json file, or the GEDCOM text itself”
- langstring
- limitinteger
- codesarray or null“Only these checks: death_before_birth, born_after_mother_death, born_after_father_death, parent_young, parent_old, married_young, long_life, possible_duplicate…”
draft_archive_requestgenerates content
“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.”
Publisher declares: read-only yes · open-world no
17 inputs, 1 required
- kindstringrequired“zags: Registry office (ZAGS): a copy of a birth/marriage/death record; state_archive: State (regional) archive: genealogical search in parish registers, revisi…”
- personstring
- bornstring
- birth_placestring
- diedstring
- death_placestring
- parentsstring
- spousestring
- relationstring“Who the requester is to the person”
- whatstring“What is requested”
- yearsstring
- placestring
- detailsstring
- archivestring“Name and address of the archive”
- requesterstring
- requester_addressstring
- projectstring
record_guidereads or searches
“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 registrat…”
Publisher declares: read-only yes · open-world no
2 inputs
- topicstring“One of: metric_book, confession_list, revision_list, household_book, wwi, wwii, repression, passenger_list, census, civil_registration_europe, latin_america, e…”
- langstring“en, ru and uk: every guide; es, pt, pl, de: the guides most used in those countries (others fall back to English)”
glossaryon 2 other serversreads or searches
“Old Russian terms from records — estates, kinship by marriage (шурин, деверь, золовка), archive citation (фонд, опись, дело, лист), administrative units, pre-1918 letters — explained.”
Publisher declares: read-only yes · open-world no
2 inputs
- termstring“A word from an old document, or empty for all”
- langstring
project_viewreads or searches
“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 re…”
Publisher declares: read-only yes · open-world no
5 inputs
- projectstring“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 …”
- whatstring
- idstring“Record id for what='record' (I1, F1, S1, L1)”
- querystring“Text for what='search'”
- langstring
project_saveon 2 other serverscreates or changes datadescribed as changing data
“Add or change a person, family, source or research lead in the project.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
7 inputs, 3 required
- projectstringrequired“Project name, the path of a gene-archive site folder, or the path of a .ged file”
- kindstringrequired
- recordobjectrequired“Fields.”
- reasonstring“Why this was added or changed — kept in the corrections log”
- source_idsarray or null“Sources (S…) that prove it”
- deleteboolean
- dry_runboolean“Check the change and show it without writing — use it to show the user what will be saved”
project_evidencereads or searches
“Review source references for individual birth/death/burial/residence and marriage events, read-only.”
Publisher declares: read-only yes · open-world no
4 inputs, 1 required
- projectstringrequired
- root_person_idstring
- generationsinteger
- limitinteger
project_policycreates or changes datadescribed as changing data
“Configure this project's policy only (dry_run by default; save within the owner's authorization).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
- projectstringrequired
- changesobjectrequired
- dry_runboolean
project_logcreates or changes datadescribed as changing data
“Write a line in the project's research log, so nobody searches the same place twice.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
7 inputs, 3 required
- projectstringrequired“Project name, the path of a gene-archive site folder, or the path of a .ged file”
- actionstringrequired“What was searched and where: 'FamilySearch index, Kolodin, Tula 1880–1890'”
- resultstringrequired“What came out — 'nothing found' is a result too”
- scopestring
- lead_idstring
- source_idstring
- outcomestring
project_coveragecreates or changes datadescribed as changing data
“What has already been read in the registers: parish → year → part → film and frames → status (complete, partial up to No.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
9 inputs, 1 required
- projectstringrequired“Project name, the path of a gene-archive site folder, or the path of a .ged file”
- actionstring“mark: save what was read; unread: what is still unread for places and years; list: everything recorded”
- entriesarray or null“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,…”
- placesarray or null“For unread/list: parishes or villages (a village is matched through the entries that name it)”
- year_frominteger or null
- year_tointeger or null
- partsarray or null“For unread: the parts to check; default births, marriages, deaths”
- dry_runboolean“For mark: show the change without writing”
- langstring
project_transfercreates or changes datadescribed as changing data
“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.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
- projectstringrequired
- directionstringrequired
- filestring“For import: path to a .ged file or the GEDCOM text”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 31 tools
Says what it returns: 100% of 31 tools
States limits, defaults or errors: 100% of 31 tools
Says when to use it: 100% of 31 tools
Items covered per tool: 4.0 of 4 on average

Counted from the listing

Parameters with a description: 45% of 150
Tools with a description: 100% of 31
Typical description length: 313 characters

The tool set

Counted from the listing

Tools: 31
Size of the list: about 9,917 tokens for an agent to load (characters ÷ 4)
Naming: 29 of 31 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 31 of 31 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the PyPI package genealogy-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "genealogy-mcp": {
      "command": "uvx",
      "args": [
        "genealogy-mcp==0.7.0"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "genealogy-mcp": {
      "command": "uvx",
      "args": [
        "genealogy-mcp==0.7.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "genealogy-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "genealogy-mcp==0.7.0"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"genealogy-mcp","type":"stdio","command":"uvx","args":["genealogy-mcp==0.7.0"]}'

Claude Code

claude mcp add --transport stdio genealogy-mcp -- uvx genealogy-mcp==0.7.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- uvx genealogy-mcp==0.7.0

This runs the publisher's code on your machine (uvx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.7.0
Latest stable: 0.7.0
Status: current
Withdrawn: no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha256-76824325f37a3c7a9…
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 0 in the last month

Source: pypistats.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.7.0 on PyPI	Exists and can be installed	matches	PyPI · 2026-10-23
Repository github.com/igormel81/genealogy-mcp	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.igormel81
GitHub owner: a personal account (igormel81)

Repository: github.com/igormel81/genealogy-mcp
Stars: 4
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 8 record checks met · 1 does not apply

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 4 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.igormel81/genealogy-mcp

Answered from the data above

Is io.github.igormel81/genealogy-mcp safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 5 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.igormel81/genealogy-mcp been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.igormel81/genealogy-mcp do?

It lists 31 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, generate content and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.igormel81/genealogy-mcp change or delete data?

5 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.igormel81/genealogy-mcp publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.7.0, the latest stable release on PyPI.

Where is the source code of io.github.igormel81/genealogy-mcp?

In github.com/igormel81/genealogy-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.AtomGraph/web-algebraWeb Algebraalso has tools that calculates or converts, creates or changes data, generates content, reads or searchescompare with this one
io.github.elpabloultron/open-legal-chileOpen Legal Chilealso has tools that calculates or converts, creates or changes data, generates content, reads or searchescompare with this one
io.github.Autario/autario-mcpalso has tools that calculates or converts, creates or changes data, generates content, reads or searchescompare with this one
app.apick/allAPICKalso has tools that calculates or converts, creates or changes data, generates content, reads or searchescompare with this one
com.narrowhighway/concordancealso has tools that calculates or converts, creates or changes data, generates content, reads or searchescompare with this one
io.github.FoodXDevelopment/foodblock-mcpalso has tools that calculates or converts, creates or changes data, generates content, reads or searchescompare with this one

Active servers whose topic is also “data-and-databases” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 5

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
1,703 msConnected after 0 redirects.
Read the inventory: 31 tools, 4 resources, 4 prompts.
2,281 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

data-and-databases

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.

Programming language

Python

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

pypi

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sha256)

package registry · 2026-10-23

Signature / provenance

does not apply

PyPI publishes no registry signature or attestation equivalent to npm dist.signatures

Dependency advisories

none known

OSV.dev · 2026-10-23

Popularity

0 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.igormel81/genealogy-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.igormel81/genealogy-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.igormel81/genealogy-mcp)](https://protocolprobe.com/mcp/servers/io.github.igormel81/genealogy-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology