# TheYtree (remote · www.theytree.com)

Public read-only MCP for the Y-chromosome haplogroup tree & Y-SNP resolution. 父系单倍群树查询与Y-SNP解析。

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

## Components

- remote · `www.theytree.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-theytree-theytree/api-v1-agent-mcp.md), [page](https://verifymcp.io/servers/com-theytree-theytree/api-v1-agent-mcp)

## Channel facts

- Endpoint: `https://www.theytree.com/api/v1/agent/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-09-28.

- **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 9 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**: 76/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1003 tokens (~111/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the TheYtree MCP server?

TheYtree is a hosted endpoint at https://www.theytree.com/api/v1/agent/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.

### Claude

```bash
claude mcp add --transport http com-theytree-theytree 'https://www.theytree.com/api/v1/agent/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-theytree-theytree": {
      "url": "https://www.theytree.com/api/v1/agent/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-theytree-theytree": {
      "type": "http",
      "url": "https://www.theytree.com/api/v1/agent/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-theytree-theytree]
url = "https://www.theytree.com/api/v1/agent/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-theytree-theytree": {
      "type": "remote",
      "url": "https://www.theytree.com/api/v1/agent/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-theytree-theytree --url 'https://www.theytree.com/api/v1/agent/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-theytree-theytree:
    url: "https://www.theytree.com/api/v1/agent/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-theytree-theytree": {
      "Transport": "http",
      "Url": "https://www.theytree.com/api/v1/agent/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-theytree-theytree -t streamable-http -u 'https://www.theytree.com/api/v1/agent/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-theytree-theytree": {
      "type": "http",
      "url": "https://www.theytree.com/api/v1/agent/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-09-28 (score 68, +1)

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

### 2026-09-26 (score 67, +1)

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

### 2026-09-25 (score 66, 0)

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

### 2026-09-24 (score 66, +1)

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

### 2026-09-22 (score 65, +1)

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

### 2026-09-20 (score 64, +1)

- [functional] Server version: 1.1.0 → 1.2.0

### 2026-09-18 (score 63, +1)

- [security] Tool “children_haplogroups” rewrote its description, which is the text the model reads
- [security] Tool “get_haplogroup_lineage” rewrote its description, which is the text the model reads
- [security] Tool “get_haplogroup_mutations” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 43% → 52%
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “children_haplogroups” added an optional parameter “limit”
- [cosmetic] “get_haplogroup_lineage” added an optional parameter “limit”
- [cosmetic] “get_haplogroup_lineage” reworded the description of “name”

### 2026-09-17 (score 62)

First indexed and scored.

## MCP tools (9)

### `list_haplogroups` (~212 tokens)

Search or list paternal haplogroups by fuzzy name and/or parent, with stable ordering for full pagination (order=name recommended). 搜索/列出父系单倍群：按名称模糊匹配、按父节点筛选，稳定排序可完整枚举。

Input parameters:

- `exclude_mf` (integer): 1=exclude MagicCube (MF) names (matches the site); default 0 keeps all / 1=排除魔方(MF)名，默认0保留全部
- `level` (integer)
- `name` (string): Fuzzy name match, e.g. O-F15365 / 名称模糊匹配
- `order` (string)
- `order_dir` (string)
- `page` (integer)
- `parent` (string): Parent node (name/hid); returns only its direct children / 父节点（名称/hid），只返回直接子节点
- `per_page` (integer)

### `get_haplogroup` (~46 tokens)

Get a single haplogroup by name / hid / SNP. 按名称/hid/SNP 获取单个单倍群详情。

Input parameters:

- `name` (string, required)

### `get_haplogroup_mutations` (~161 tokens)

List a haplogroup defining (equivalent) mutations (paternal / Y tree only). 获取某单倍群的等价突变（defining SNPs）列表（仅父系 Y 树）。

Input parameters:

- `compact` (integer): 1=compact fields only (snpid,snpname,haplogroup), much smaller / 1=仅返回精简字段，显著缩小体积
- `fields` (string): Custom fields (comma-separated), e.g. "snpname,location" / 自定义返回字段
- `include_under_observation` (integer)
- `name` (string, required)
- `page` (integer)
- `per_page` (integer)

### `get_haplogroup_lineage` (~139 tokens)

Get the lineage chain from a haplogroup up to ROOT. Use limit to fetch only the most recent N levels (e.g. limit=2 for the node + its parent). 获取某单倍群上溯到 ROOT 的谱系链；可用 limit 只取最近 N 级（如 limit=2 即该节点与其直接父级）。

Input parameters:

- `limit` (integer): Return only the most recent N levels (default: all). / 只返回最近 N 级，默认全部
- `name` (string, required): Haplogroup name or hid / 单倍群名称或 hid

### `children_haplogroups` (~114 tokens)

Get the direct children of a haplogroup (for level-by-level traversal). Use limit for the N largest subclades only. 获取直接子节点（逐层遍历）；可用 limit 只看最大的 N 个分支。

Input parameters:

- `limit` (integer): Return only the N largest children by size (default: all). / 只返回规模最大的 N 个直接子节点，默认全部
- `name` (string, required): Haplogroup name or hid / 单倍群名称或 hid

### `resolve_snp` (~52 tokens)

Resolve a SNP name to its haplogroup and return equivalent names (merged-name variants supported). 将 SNP 名解析到所属单倍群并返回等价名。

Input parameters:

- `snpname` (string, required)

### `resolve_snps` (~83 tokens)

Batch-resolve up to 200 SNP names to their haplogroups (for reading a whole Y-SNP panel). 批量解析多个 SNP 名到所属单倍群（≤200/次）。

Input parameters:

- `snpnames` (array, required): Array of SNP names, e.g. ["M269","M122","F15365"] / SNP 名数组

### `subtree_haplogroups` (~145 tokens)

Get a haplogroup subtree. Defaults to 6 levels (matches the site); small branches (root endcounts<=600) fully expand; max_depth overrides. Truncated boundary nodes carry has_children. 取子树：默认 6 层，小支(endcounts<=600)全展开，可传 max_depth；截断边界带 has_children。

Input parameters:

- `max_depth` (integer): Max levels relative to root (optional). Default 6; unlimited if root endcounts<=600 / 相对根最大层数（可选），默认6
- `name` (string, required): Subtree root name/hid / 子树根节点名称/hid

### `get_api_info` (~51 tokens)

Get service meta: summary, auth, dataset size (haplogroups / mutation records), and the tool list. 获取本服务元信息：简介、鉴权、数据集规模、工具清单。

## Diagnostics

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

## Score history

- 2026-09-28: 68
- 2026-09-27: 67
- 2026-09-26: 67
- 2026-09-25: 66
- 2026-09-24: 66
- 2026-09-23: 65
- 2026-09-22: 65
- 2026-09-21: 64
- 2026-09-20: 64
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 62

## Common questions

### What is the TheYtree MCP server?

TheYtree is an MCP server listed in the public MCP registry as com.theytree/theytree. Public read-only MCP for the Y-chromosome haplogroup tree & Y-SNP resolution. 父系单倍群树查询与Y-SNP解析。 This page covers its hosted endpoint (https://www.theytree.com/api/v1/agent/mcp).

### Is the TheYtree MCP server safe to use?

TheYtree scores 68 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 TheYtree MCP server expose?

TheYtree exposes 9 tools: list_haplogroups, get_haplogroup, get_haplogroup_mutations, get_haplogroup_lineage, children_haplogroups, and 4 more. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.

### Does the TheYtree MCP server require authentication?

No. We connected to TheYtree without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TheYtree MCP server still maintained?

TheYtree is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.theytree.com/api/v1/agent/mcp
- Website: https://www.theytree.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-theytree-theytree/api-v1-agent-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-theytree-theytree/api-v1-agent-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-theytree-theytree/api-v1-agent-mcp