# io.github.HumanLineage/wt (remote · humanlineage.org)

Human Lineage MCP server — search and query the public genealogical graph of all humanity

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `humanlineage.org`: 70/100 (this document), [markdown](https://verifymcp.io/servers/humanlineage-wt/api-mcp.md), [page](https://verifymcp.io/servers/humanlineage-wt/api-mcp)

## Channel facts

- Endpoint: `https://humanlineage.org/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 371 tokens (~61/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http humanlineage-wt https://humanlineage.org/api/mcp
```

### Codex

```toml
[mcp_servers.humanlineage-wt]
url = "https://humanlineage.org/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "humanlineage-wt": {
      "type": "remote",
      "url": "https://humanlineage.org/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add humanlineage-wt --url https://humanlineage.org/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  humanlineage-wt:
    url: "https://humanlineage.org/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "humanlineage-wt": {
      "type": "http",
      "url": "https://humanlineage.org/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (6)

### `search_person` (~64 tokens)

Search person

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

Input parameters:

- `limit` (integer): Max results (default 10, max 20)
- `query` (string, required): Name (or part of a name) to search for

### `get_person` (~46 tokens)

Get person

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

Input parameters:

- `id` (string, required): Person ID, e.g. as returned by search_person

### `get_relatives` (~66 tokens)

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.

Input parameters:

- `id` (string, required): Person ID to look up relatives for

### `get_family_image` (~102 tokens)

Get family image

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.

Input parameters:

- `id` (string, required): Person ID to render a family card for

### `search_place` (~47 tokens)

Search place

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

Input parameters:

- `query` (string, required): Place name (or part of it) to search for

### `get_place` (~46 tokens)

Get place

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

Input parameters:

- `id` (string, required): Place ID, e.g. as returned by search_place

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/humanlineage-wt/api-mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://humanlineage.org/api/mcp
- Repository: https://github.com/HumanLineage/WT
- Changelog RSS feed: https://verifymcp.io/servers/humanlineage-wt/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/humanlineage-wt/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/humanlineage-wt/api-mcp