Koskamo

Human Lineage MCP

A public MCP server that allows AI agents to search and query a global genealogical graph containing over 52.9 million people and 67.6 million relationships. It supports tools for searching persons, retrieving person details, finding relatives, accessing family images, and searching places.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Human Lineage MCP logo, by Human LineageCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by Human Lineage
MCP endpoint (Streamable HTTP)
https://humanlineage.org/api/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

6 of 6 have a description · 0 of 6 declare behavior hints · 6 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for a person by name or place of birth
  • Retrieve detailed person profiles including dates and relationships
  • Find relatives of a specific individual
  • Search for historical places

Source and maintenance

Community listingRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
mcp-typescript server on vercel 0.1.0
MCP protocol negotiated in check
2025-11-25
Tools
6 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

6 advertised

search_person — Search person
Advertised by the server during the last successful anonymous check.

Search the Human Lineage genealogical graph for a person by name. Returns matches with their profile URL.

search_person input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Max results (default 10, max 20)"
    },
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "Name (or part of a name) to search for"
    }
  }
}
get_person — Get person
Advertised by the server during the last successful anonymous check.

Get full details for a person by their Human Lineage ID, including a link to their profile.

get_person input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Person ID, e.g. as returned by search_person"
    }
  }
}
get_relatives — Get relatives
Advertised by the server during the last successful anonymous check.

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.

get_relatives input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Person ID to look up relatives for"
    }
  }
}
get_family_image — Get family image
Advertised by the server during the last successful anonymous check.

Returns a markdown image (![...](url)) 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.

get_family_image input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Person ID to render a family card for"
    }
  }
}
search_place — Search place
Advertised by the server during the last successful anonymous check.

Search the Human Lineage genealogical graph for a place by name. Returns matches with their place URL.

search_place input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "Place name (or part of it) to search for"
    }
  }
}
get_place — Get place
Advertised by the server during the last successful anonymous check.

Get details for a place by its Human Lineage ID, including its hierarchy and recorded person count.

get_place input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Place ID, e.g. as returned by search_place"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
829 ms
95th percentile latency
829 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 829 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http human-lineage-mcp https://humanlineage.org/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add human-lineage-mcp --url https://humanlineage.org/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable human-lineage-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "human-lineage-mcp": {
      "url": "https://humanlineage.org/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "human-lineage-mcp": {
      "type": "streamableHttp",
      "url": "https://humanlineage.org/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start human-lineage-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "human-lineage-mcp": {
      "type": "http",
      "url": "https://humanlineage.org/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http human-lineage-mcp https://humanlineage.org/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://humanlineage.org/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "human-lineage-mcp": {
      "serverUrl": "https://humanlineage.org/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Human Lineage MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.