MCP.Market

AncestralFire MCP server

online · 100% uptime
by ancestral-fire.com·com.ancestral-fire/ancestralfire·v0.1.1
No reviews yet

Family history and genealogy in your AI: your tree and FamilySearch, with a source for every fact.

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed AncestralFire yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AncestralFire tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How AncestralFire compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
786 ms
faster than 17% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-03, latest 2026-11-02, typically one every 30 days.

Install AncestralFire in Claude Code, Cursor or VS Code

claude mcp add --transport http ancestralfire https://mcp.ancestral-fire.com/mcp
Add to Cursor

AncestralFire: common questions

Is AncestralFire MCP server safe?
Mostly: it is graded B (77/100). Read the AncestralFire safety report
How do I install AncestralFire?
It runs remotely at mcp.ancestral-fire.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does AncestralFire need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AncestralFire maintained?
The latest release is v0.1.1.
Is AncestralFire up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does AncestralFire compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 786 ms (faster than 17% of 30,031 servers). Full comparison.