io.github.HumanLineage/wt
REMOTE · HUMANLINEAGE.ORG · SCANNED SEP 22
Human Lineage MCP server — search and query the public genealogical graph of all humanity
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 371 tokens (~61/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.HumanLineage/wt MCP server?
io.github.HumanLineage/wt is a hosted endpoint at https://humanlineage.org/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · humanlineage.org
claude mcp add --transport http humanlineage-wt 'https://humanlineage.org/api/mcp'
{
"mcpServers": {
"humanlineage-wt": {
"url": "https://humanlineage.org/api/mcp"
}
}
} {
"servers": {
"humanlineage-wt": {
"type": "http",
"url": "https://humanlineage.org/api/mcp"
}
}
} [mcp_servers.humanlineage-wt] url = "https://humanlineage.org/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"humanlineage-wt": {
"type": "remote",
"url": "https://humanlineage.org/api/mcp",
"enabled": true
}
}
} openclaw mcp add humanlineage-wt --url 'https://humanlineage.org/api/mcp' --transport streamable-http
mcp_servers:
humanlineage-wt:
url: "https://humanlineage.org/api/mcp" {
"McpServers": {
"humanlineage-wt": {
"Transport": "http",
"Url": "https://humanlineage.org/api/mcp"
}
}
} assistant mcp add humanlineage-wt -t streamable-http -u 'https://humanlineage.org/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 21 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 17 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 16 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Sept 26 +64
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 10 Sept 26 −64
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://humanlineage.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=humanlineage.org | CN=YE1,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 56ef015d165f8e9c2d86ffbbe0dd64b84da |
| SANs: *.humanlineage.org, humanlineage.org | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of humanlineage.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| humanlineage.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://humanlineage.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://humanlineage.org/api/mcp | HTTPS enforced | 302 | https://humanlineage.org/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_family_image Get family image ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Person ID to render a family card for |
No output schema declared.
No examples provided.
get_person Get person ~46
Get full details for a person by their Human Lineage ID, including a link to their profile.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Person ID, e.g. as returned by search_person |
No output schema declared.
No examples provided.
get_place Get place ~46
Get details for a place by its Human Lineage ID, including its hierarchy and recorded person count.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Place ID, e.g. as returned by search_place |
No output schema declared.
No examples provided.
get_relatives Get relatives ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Person ID to look up relatives for |
No output schema declared.
No examples provided.
search_person Search person ~64
Search the Human Lineage genealogical graph for a person by name. Returns matches with their profile URL.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10, max 20) |
| query | string | yes | Name (or part of a name) to search for |
No output schema declared.
No examples provided.
search_place Search place ~47
Search the Human Lineage genealogical graph for a place by name. Returns matches with their place URL.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Place name (or part of it) to search for |
No output schema declared.
No examples provided.
What is the io.github.HumanLineage/wt MCP server?
io.github.HumanLineage/wt is an MCP server listed in the public MCP registry as io.github.HumanLineage/wt. Human Lineage MCP server, search and query the public genealogical graph of all humanity. This page covers its hosted endpoint (https://humanlineage.org/api/mcp).
Is the io.github.HumanLineage/wt MCP server safe to use?
io.github.HumanLineage/wt scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.HumanLineage/wt MCP server expose?
io.github.HumanLineage/wt exposes 6 tools: search_person, get_person, get_relatives, get_family_image, search_place, get_place. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.
Does the io.github.HumanLineage/wt MCP server require authentication?
No. We connected to io.github.HumanLineage/wt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.HumanLineage/wt MCP server still maintained?
io.github.HumanLineage/wt is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.