TheYtree
REMOTE · WWW.THEYTREE.COM · SCANNED SEP 28
Public read-only MCP for the Y-chromosome haplogroup tree & Y-SNP resolution. 父系单倍群树查询与Y-SNP解析。
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 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. 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 Usability76
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · www.theytree.com
claude mcp add --transport http com-theytree-theytree 'https://www.theytree.com/api/v1/agent/mcp'
{
"mcpServers": {
"com-theytree-theytree": {
"url": "https://www.theytree.com/api/v1/agent/mcp"
}
}
} {
"servers": {
"com-theytree-theytree": {
"type": "http",
"url": "https://www.theytree.com/api/v1/agent/mcp"
}
}
} [mcp_servers.com-theytree-theytree] url = "https://www.theytree.com/api/v1/agent/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-theytree-theytree": {
"type": "remote",
"url": "https://www.theytree.com/api/v1/agent/mcp",
"enabled": true
}
}
} openclaw mcp add com-theytree-theytree --url 'https://www.theytree.com/api/v1/agent/mcp' --transport streamable-http
mcp_servers:
com-theytree-theytree:
url: "https://www.theytree.com/api/v1/agent/mcp" {
"McpServers": {
"com-theytree-theytree": {
"Transport": "http",
"Url": "https://www.theytree.com/api/v1/agent/mcp"
}
}
} assistant mcp add com-theytree-theytree -t streamable-http -u 'https://www.theytree.com/api/v1/agent/mcp'
{
"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.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +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.
- 25 Sept 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
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +1
- Server version: 1.1.0 → 1.2.0 functional
- 18 Sept 26 +1
- 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 security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 43% → 52% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “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” cosmetic
- 17 Sept 26 62
First indexed and scored.
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 28 Sept 2026 · Probed https://www.theytree.com/api/v1/agent/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.theytree.com | CN=LiteSSL RSA CA 2025,O=TrustAsia Technologies\, Inc.,C=CN | 13 Jul 2026 | 11 Oct 2026 | RSA 2048 | SHA256-RSA | 70b7b9613b46bd6ee66e55ee2ad221797e96c89 |
| SANs: *.theytree.com, theytree.com | ||||||
| CN=LiteSSL RSA CA 2025,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN | 21 Oct 2025 | 21 Oct 2030 | RSA 2048 | SHA256-RSA | 2ce54b63f5e07b62f6ba869622995dadf627f82e |
| CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL | 7 Oct 2025 | 14 Jan 2029 | RSA 4096 | SHA384-RSA | b2dc4c34932d709cd4bf0b099401695c |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.theytree.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| theytree.com. | 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=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.theytree.com/api/v1/agent/mcp | Verified | 200 | |
| http (plaintext) | http://www.theytree.com/api/v1/agent/mcp | HTTPS enforced | 301 | https://www.theytree.com/api/v1/agent/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 →
children_haplogroups ~114
Get the direct children of a haplogroup (for level-by-level traversal). Use limit for the N largest subclades only. 获取直接子节点（逐层遍历）；可用 limit 只看最大的 N 个分支。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Return only the N largest children by size (default: all). / 只返回规模最大的 N 个直接子节点，默认全部 |
| name | string | yes | Haplogroup name or hid / 单倍群名称或 hid |
No output schema declared.
No examples provided.
get_api_info ~51
Get service meta: summary, auth, dataset size (haplogroups / mutation records), and the tool list. 获取本服务元信息：简介、鉴权、数据集规模、工具清单。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_haplogroup ~46
Get a single haplogroup by name / hid / SNP. 按名称/hid/SNP 获取单个单倍群详情。
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
get_haplogroup_lineage ~139
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 即该节点与其直接父级）。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Return only the most recent N levels (default: all). / 只返回最近 N 级，默认全部 |
| name | string | yes | Haplogroup name or hid / 单倍群名称或 hid |
No output schema declared.
No examples provided.
get_haplogroup_mutations ~161
List a haplogroup defining (equivalent) mutations (paternal / Y tree only). 获取某单倍群的等价突变（defining SNPs）列表（仅父系 Y 树）。
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| page | integer | – | – |
| per_page | integer | – | – |
No output schema declared.
No examples provided.
list_haplogroups ~212
Search or list paternal haplogroups by fuzzy name and/or parent, with stable ordering for full pagination (order=name recommended). 搜索/列出父系单倍群：按名称模糊匹配、按父节点筛选，稳定排序可完整枚举。
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
resolve_snp ~52
Resolve a SNP name to its haplogroup and return equivalent names (merged-name variants supported). 将 SNP 名解析到所属单倍群并返回等价名。
| Name | Type | Req | Description |
|---|---|---|---|
| snpname | string | yes | – |
No output schema declared.
No examples provided.
resolve_snps ~83
Batch-resolve up to 200 SNP names to their haplogroups (for reading a whole Y-SNP panel). 批量解析多个 SNP 名到所属单倍群（≤200/次）。
| Name | Type | Req | Description |
|---|---|---|---|
| snpnames | array | yes | Array of SNP names, e.g. ["M269","M122","F15365"] / SNP 名数组 |
No output schema declared.
No examples provided.
subtree_haplogroups ~145
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。
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | integer | – | Max levels relative to root (optional). Default 6; unlimited if root endcounts<=600 / 相对根最大层数（可选），默认6 |
| name | string | yes | Subtree root name/hid / 子树根节点名称/hid |
No output schema declared.
No examples provided.
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.