Databases
humanlineage.org
MCP server for searching and retrieving genealogical data from the Human Lineage graph, including person details, relatives, family-tree images, and places.
ENDPOINT 1
https://humanlineage.org/api/mcp
MCP server metadata
- Name
- mcp-typescript server on vercel
- Version
- 0.1.0
Known tools 6
get_personGet full details for a person by their Human Lineage ID, including a link to their profile.
Inferred read-onlyget_relativesGet the immediate family (parents, children, spouses) of a person as TEXT, with profile URLs.
Inferred read-onlyget_family_imageReturns a markdown image () of a visual family-tree card showing a person's parents, spouse and children.
Inferred read-onlyget_placeGet details for a place by its Human Lineage ID, including its hierarchy and recorded person count.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mcp-typescript-server-on-vercel]
url = "https://humanlineage.org/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mcp-typescript-server-on-vercel": {
"type": "http",
"url": "https://humanlineage.org/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mcp-typescript-server-on-vercel
Remote MCP URL: https://humanlineage.org/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mcp-typescript-server-on-vercel": {
"url": "https://humanlineage.org/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mcp-typescript-server-on-vercel": {
"type": "http",
"url": "https://humanlineage.org/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mcp-typescript-server-on-vercel",
"transport": "streamable-http",
"url": "https://humanlineage.org/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.