wt MCP server
io.github.HumanLineage/wtHumanLineagestreamable-httpv0.1.0Scanned
Human Lineage MCP server — search and query the public genealogical graph of all humanity
6 tools: 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the wt MCP server can do
The wt MCP server is published by the GitHub account HumanLineage. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Only reads 6Show 6 read-only tools
get_family_imageReturns a markdown image of a visual family-tree card showing a person's parents, spouse and children, as a picture of the family.No findings
Why it is in this group
- The name "get_family_image" says "get": a word for reading.
Description, as the server wrote it Returns a markdown image of a visual family-tree card showing a person's parents, spouse and children, as a picture of the family.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get family image
get_personGet full details for a person by their Human Lineage ID, including a link to their profile.No findings
Why it is in this group
- The name "get_person" says "get": a word for reading.
Description, as the server wrote it Get full details for a person by their Human Lineage ID, including a link to their profile.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get person
get_placeGet details for a place by its Human Lineage ID, including its hierarchy and recorded person count.No findings
Why it is in this group
- The name "get_place" says "get": a word for reading.
Description, as the server wrote it Get details for a place by its Human Lineage ID, including its hierarchy and recorded person count.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get place
get_relativesGet the immediate family (parents, children, spouses) of a person as text, with profile URLs.No findings
Why it is in this group
- The name "get_relatives" says "get": a word for reading.
Description, as the server wrote it Get the immediate family (parents, children, spouses) of a person as text, with profile URLs.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get relatives
search_personSearch the Human Lineage genealogical graph for a person by name.No findings
Why it is in this group
- The name "search_person" says "search": a word for reading.
Description, as the server wrote it Search the Human Lineage genealogical graph for a person by name. Returns matches with their profile URL.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Search person
search_placeSearch the Human Lineage genealogical graph for a place by name.No findings
Why it is in this group
- The name "search_place" says "search": a word for reading.
Description, as the server wrote it Search the Human Lineage genealogical graph for a place by name. Returns matches with their place URL.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Search place
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 changed.~6 changedView diff
- Changed:get_family_imageOnly readsdescriptionannotations
- Changed:get_personOnly readsinputSchemaannotations
- Changed:get_placeOnly readsinputSchemaannotations
- Changed:get_relativesOnly readsdescriptionannotations
- Changed:search_personOnly readsannotations
- Changed:search_placeOnly readsannotations
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wt https://humanlineage.org/api/mcpclaude mcp add --transport http wt https://humanlineage.org/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wt__search_person",
"mcp__wt__get_person",
"mcp__wt__get_relatives",
"mcp__wt__get_family_image",
"mcp__wt__search_place",
"mcp__wt__get_place"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wt. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.HumanLineage/wt/verify?hash=a4434c9628dfccf37c63c5a7cfa14095a152791028f9b9ec3cedf89754b6b155" | jq -e '.changed == false'Pinned hash a4434c9628df, from Nov 15, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.HumanLineage/wt/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.HumanLineage/wt)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.
wt MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the wt MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the wt MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the wt MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the wt MCP server have?
- 6 tools: 6 read. search_person, get_person, get_relatives, get_family_image, search_place and get_place.
Does the wt MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the wt MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the wt MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.