mcpbeat Sign in

AncestralFire MCP Server

by ancestral-fire Your server? Claim it
answering

AncestralFire is answering right now. Last checked 4 min ago.

There's more to your family tree than names and dates.

Uptime history 9 days of history · worst day 98%
9 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
693 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

AncestralFire does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add ancestralfire --transport http https://mcp.ancestral-fire.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ancestralfire": {
      "url": "https://mcp.ancestral-fire.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ancestralfire]
url = "https://mcp.ancestral-fire.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ancestralfire": {
      "url": "https://mcp.ancestral-fire.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ancestralfire": {
      "url": "https://mcp.ancestral-fire.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.ancestral-fire.com/mcp streamable-http sign-in 779 ms 4 min ago

Alternatives to AncestralFire

same job, measured the same way
Buna
by heybuna

The family food app your agent operates.

answering
Firebase Deploy Leak Audit
by jmshinhwa

Reads firebase.json and names the files your next firebase deploy would publish to the open web

117 installs/wk local only
The Margin
by themarginapp

Notes, boards, habits, money and family life in one place your AI can read and act on.

answering
MoreLike
by morelike

Track the TV and films you watch, and find more like them, by talking to your own AI.

answering
Audo
by audo

Audio and video tools for your AI assistant: remove noise, enhance voices, transcribe, and more.

answering
Refsee
by refsee

Search visual references, explore similar frames and manage your Refsee moodboards.

answering
Fulcra
by fulcradynamics

Use your Fulcra secure context lake to collaborate with other agents, read and write data, and more

1 380 installs/wk answering
Lunch Money MCP
by juftin

MCP-first access to your Lunch Money data.

local only

AncestralFire — questions

Answers built from our own checks of this server.

Why is there no tool list for AncestralFire?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is AncestralFire working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 693 ms. The bar chart above shows every period we have measured.
How do I connect AncestralFire?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to AncestralFire?
No API key is involved. AncestralFire answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is AncestralFire?
It answers our handshake in 693 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.