Wt MCP Server
io.github.HumanLineage/wt
answering
Wt is answering right now. Last checked 10 min ago. It exposes 6 tools.
Human Lineage MCP server — search and query the public genealogical graph of all humanity
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
40 hours of history · worst hour 75%
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
262 ms
Response time
average over 24h
open, no key
Access
streamable-http
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
run in your terminal
claude mcp add wt --transport http https://humanlineage.org/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"wt": {
"url": "https://humanlineage.org/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.wt]
url = "https://humanlineage.org/api/mcp".cursor/mcp.json
{
"mcpServers": {
"wt": {
"url": "https://humanlineage.org/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"wt": {
"url": "https://humanlineage.org/api/mcp"
}
}
}Available tools 6
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
person
get_person
Get full details for a person by their Human Lineage ID, including a link to their profile.
search_person
Search the Human Lineage genealogical graph for a person by name. Returns matches with their profile URL.
place
get_place
Get details for a place by its Human Lineage ID, including its hierarchy and recorded person count.
search_place
Search the Human Lineage genealogical graph for a place by name. Returns matches with their place URL.
family
get_family_image
Returns a markdown image () of a visual family-tree card showing a person's parents, spouse and children. Use this — not get_relatives — whenever the user asks to see, show, view, or display a family tree, family diagram, or picture of the family. IMPORTANT: include the returned markdown image line verbatim in your reply so it renders for the user.
relatives
get_relatives
Get the immediate family (parents, children, spouses) of a person as TEXT, with profile URLs. Use get_family_image instead if the user wants to see a picture/visual/graphic of the family tree.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://humanlineage.org/api/mcp | streamable-http | answering | 280 ms | 10 min ago |
Wt — questions
Answers built from our own checks of this server.
What can Wt do?
It exposes 6 tools, read directly from the server on our last check. Among them: get_family_image, get_person, get_place, get_relatives, search_person, search_place. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Wt mostly used for?
Its tools cluster around person and place. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Wt working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 262 ms. The bar chart above shows every period we have measured.
Is Wt still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Wt?
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.
Does Wt need an API key?
No. Wt completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Wt?
It answers our handshake in 262 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.