Find an app
Account
Toggle menu

Use in your browser

Validate your GEDCOM file

Validate a deceased-only, public-sample, synthetic, or redacted GEDCOM 7 file against the FamilySearch GEDCOM-registries corpus. Never submit living-person names, dates, locations, contact details, identifiers, or relationships. Input is not retained after processing, and no record values are echoed.

Guest includes 50 lifetime app requests. Create a free account for 100 app requests each calendar month. One allowance across every app, in your browser and your agent.One allowance across every app, in your browser and your agent. Manage usage

GEDCOM File Check

Connect agent

Guest access is available after setup. Full account linking verified by PowMCP: Claude only.

GEDCOM check

Validate one deceased-only, public-sample, synthetic, or redacted GEDCOM 7 file with rule-class evidence.

Fetching and validating one file can take up to 110 seconds.

GEDCOM file source

Only the active source is sent. You can switch without losing what you entered.

A deceased-only, public-sample, synthetic, or redacted .ged file. Never submit living-person data.

Allowed range: 1–1000 · whole numbers

The engine reports at most 100 findings per file

Add GEDCOM File Check to your agent

Connect this app on its own. Add other PowMCP apps whenever your agent needs another job done.

Open the apps workspace A glowing app tile clicking into a slot on a dark agent device, with the PowMCP app box behind it

Connect directly

Choose your agent. Each button opens a new tab with only this app's endpoint ready to add.

Use another agent

Copy one ready-to-send prompt for any agent that supports remote MCP connections.

Manual endpoint, JSON, and terminal commands

For clients that require manual configuration, use this app-only endpoint, its JSON entry, or one terminal command.

ChatGPT: enable Developer mode in Settings → Security and login, then add this MCP endpoint from the Plugins page. Availability depends on your account and workspace policy. PowMCP has not yet verified ChatGPT account linking. OpenAI setup guide

https://powmcp.com/gedcom-file-check/mcp
{
  "mcpServers": {
    "powmcp-gedcom-file-check": {
      "type": "http",
      "url": "https://powmcp.com/gedcom-file-check/mcp"
    }
  }
}

Terminal agents add this app with one command:

Claude Code
claude mcp add --transport http powmcp-gedcom-file-check https://powmcp.com/gedcom-file-check/mcp
Codex CLI
codex mcp add powmcp-gedcom-file-check --url https://powmcp.com/gedcom-file-check/mcp
Gemini CLI
gemini mcp add --transport http powmcp-gedcom-file-check https://powmcp.com/gedcom-file-check/mcp

Manage, disable, or remove this connection in your agent's own MCP settings. PowMCP does not label an external connection as installed without confirmation from that client.

Proof

What it does

Validate a hosted GEDCOM 7 genealogy file against the GEDCOM-registries corpus with the reference GedValidate engine, with exact rule-class evidence: real corpus validation, not a line-grammar parse

Validate one deceased-only, public-sample, synthetic, or redacted GEDCOM 7 genealogy file against the bundled FamilySearch/GEDCOM-registries corpus using the reference ArmidaleSoftware GedValidate engine with exact tag-context, cardinality, enumeration, and cross-reference evidence, or compare two same-lineage safe samples with GedCompare, with a clear structure-conformance-versus-genealogical-truth boundary.

Category
Developer Tools

Request cost1 completed result

Guests get 50 lifetime app requests. Free accounts get 100 each calendar month.

Tools in this app

01

GEDCOM 7 Conformance Check

gedcom_check

Fetch one directly hosted deceased-only, public-sample, synthetic, or redacted GEDCOM 7 .ged file by URL (or accept small safe GEDCOM 7 text inline), magic/text-sniff that it is GEDCOM (the content must start with `0 HEAD` and carry a GEDC/VERS 7.0 header, checked by content not MIME), and validate it with the reference ArmidaleSoftware GedValidate engine against the bundled FamilySearch/GEDCOM-registries corpus (465 structure definitions, 15 enumeration sets, calendar/data-type grammar), run offline in a no-network sandbox. Never submit living-person names, dates, locations, contact details, identifiers, or relationships. Returns conformance pass/fail, counts by rule class (tag-context, cardinality, enumeration, cross-reference, calendar-grammar), bounded findings each with line context and the engine message, the pinned engine and corpus versions, and distinguished states (not-gedcom vs a GEDCOM that fails the corpus; version-not-7 vs unsupported-version; no-findings vs not-checked). Use for one-file conformance and diagnosis: 'is this valid GEDCOM 7', 'is it registries-conformant', 'what structure/enum/cardinality/xref problems does it have'. When a clearly identified public test, synthetic, redacted, or deceased-only sample is supplied, a broader handoff-readiness question still calls for the supported structural check. Scope the answer to the supplied bytes, not a personal whole tree, permission to share, or historical truth. A public URL alone does not establish safe input; ask for clarification when its safety status is genuinely unknown. Supply exactly one of url or text. A pass means only that the file conforms to GEDCOM 7 structure and the pinned corpus (it never claims the recorded relationships, names, or dates are historically correct), and it does not validate an unhosted local file on your machine or a GEDZIP (.gedz) container. Downloads and validates a live file under a 110-second call deadline; tell the user before calling.

02

GEDCOM 7 Structural Compare

gedcom_compare

Compare exactly two directly hosted deceased-only, public-sample, synthetic, or redacted GEDCOM 7.0 files of the same lineage with the reference ArmidaleSoftware GedCompare engine, and report the structural diff keyed by structure/tag path, with values omitted for privacy. Never submit living-person names, dates, locations, contact details, identifiers, or relationships. Fetches both files, magic/text-sniffs each is GEDCOM 7, validates each against the bundled FamilySearch/GEDCOM-registries corpus for its conformance state, then diffs them offline in a no-network sandbox. Returns per-file sha256, detected version, and conformance; a comparability note; the added/removed structure counts and bounded tag-path lists; and a ranking by conformance state only. Use for what-changed-between-two-safe-sample-exports and before/after questions. The tool reports not-comparable if they do not line up, so do not pre-check that yourself. Automated structural comparison only: a smaller diff never means one tree is more correct or the genealogy is truer, and it does not validate unhosted local files. Fetches and diffs two live files under one shared 110-second call deadline; tell the user before calling.

GEDCOM File Check questions

Scope and boundaries for GEDCOM File Check.

01What can I check with GEDCOM File Check?

Validate the public maximal70.ged sample, whose text begins with 0 HEAD and declares GEDC/VERS 7.0, with a bounded findings list; or compare the remarriage1 and remarriage2 samples as baseline and revision.

02How should I read the result?

Start with checked, status, and conforms: only checked with conforms true means the pinned GedValidate engine found no GEDCOM 7 corpus violation. Fix the first line-located finding and rerun; not-GEDCOM, wrong-version, and unsupported-version mean validation never ran, while truncation means more findings may exist. Compare structure only for files whose shared genealogy lineage you already know, because the tool does not establish lineage or genealogical truth.

03What are its limits?

Submit only deceased-only, synthetic, public-sample, or redacted data—never living-person details. This checks GEDCOM 7 structure against the bundled corpus, not genealogical truth; GEDZIP containers and unhosted local files are outside the URL workflow.