中文 AI 可引用性（GEO/AEO）体检
REMOTE · SAVANTCAT.CN
中文站能否被豆包/DeepSeek/文心/Kimi 抓取、读懂、引用：可引用性审计、信源池占位探测、五大指标测量、修复计划、观测时序追踪
Available components
Last scanned (8 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1541 tokens (~154/item across 10 items; 7 tools + 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.97 ▲ functional
- 3 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +38
- Authorization: unverified → partial ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → 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 5 Nov 2026 · Probed https://savantcat.cn/mcp-geo
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=savantcat.cn | CN=YE1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 57cf621a513d70503b676905c84236a8e79 |
| SANs: savantcat.cn, www.savantcat.cn | ||||||
| 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 savantcat.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | present | 33094 | 8 | Verified |
| savantcat.cn. | 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; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), magnetometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://savantcat.cn/mcp-geo | Verified | 200 | |
| http (plaintext) | http://savantcat.cn/mcp-geo | HTTPS enforced | 301 | https://savantcat.cn/mcp-geo |
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 →
audit_cn_citability ~199
审计一个网站/页面能否被中文 AI 搜索（豆包、DeepSeek、文心、Kimi 等）抓取、解析与引用。 一次抓取完成六层检查：可抓取（含中国爬虫矩阵与边缘层拦截实测）、可解析、可引用、 实体一致、分发、可信可自验；返回 0-100 分与 A-F 等级、逐项证据、优先修复清单。 用途场景：客户站点体检、上线前自检；传 compare_with 可做竞品对比（逐层与逐项差异）。 注意：只做确定性检查，不调用大模型；评分口径见 scoring_version。
| Name | Type | Req | Description |
|---|---|---|---|
| compare_with | string | – | – |
| include_raw | boolean | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diff_observations ~184
对比某 identity 的**最近两次观测**，判定提升/退化/中性（带阈值与样本门槛说明）。 判定门槛：相对变化 >= 20% **且** 绝对变化 >= 0.05 才算"显著"（severity: rise / sharp_drop）。 样本 n < 20 一律返回 severity=low_n，**不给出升降结论**——这是防误报的硬门。 Args: identity: 品牌名或域名 kind: 观测类型，留空取全部 series: 题集/口径标识，留空取全部
| Name | Type | Req | Description |
|---|---|---|---|
| identity | string | yes | – |
| kind | string | – | – |
| series | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_signals ~85
列出**已检测到的变化信号**（visibility 提升/退化等），带生命周期（first_seen / resolved_at）。 Args: status: open（未解决，默认）/ resolved（已解决）/ all limit: 最多返回条数
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
plan_fixes ~124
按缺口生成优先修复计划（可直接交给客户或工程执行）。 两种用法：① 传 fail_ids（逗号分隔的自查项编号，如 "L1-3,L2-4"）；② 传 url，工具先审计再出计划。 返回：按权重排序的修复项、每项「为什么」「怎么补」「验收方式」。
| Name | Type | Req | Description |
|---|---|---|---|
| fail_ids | string | – | – |
| top | integer | – | – |
| url | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
probe_source_pool ~198
探测一个中文问题在信源池里的实际占位分布，并判断你的品牌/域名是否在池子里。 原理：AI 答案只能引用「已进入检索池」的来源。若目标问题下主流信源被平台型站点 （知乎/公众号转载站/百家号/CSDN 等）占满而你不在其中，再好的站内优化也不会被引用。 返回：结果域名分布、平台归类、是否命中你的品牌/域名、同题竞品域名清单、建议动作。 参数：question 用户真实会问的问题原话；brand 品牌词（如「合尘猫」）；domain 你的域名（如 savantcat.cn）。
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| domain | string | – | – |
| question | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query_history ~229
查某个品牌/域名在**历史观测**中的时序（多次采样的轨迹）。 数据来自本工作室按周期采样的记录（写入走 CLI，服务本身只读）。 **只在同一 series（同一题集/同一口径）内纵向比较**，不同 series 的值不可直接比大小。 Args: identity: 品牌名或域名，如 "合尘猫" / "savantcat.cn" kind: 观测类型，留空取全部。常用：mention_rate(提及率) / citation_rate(引用率) / visibility_score(可见度分) / rank(排名) / robots_policy / llms_txt series: 题集/口径标识，留空取全部 limit: 每条 series 最多返回的最新点数
| Name | Type | Req | Description |
|---|---|---|---|
| identity | string | yes | – |
| kind | string | – | – |
| limit | integer | – | – |
| series | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
score_visibility ~309
按五大核心指标 + 语义角色分权，计算 AI 搜索可见度并输出可自验的测量报告。 输入 samples 为 JSON 字符串： {"brand":"合尘猫","domain":"savantcat.cn","baseline_negative":3, "fact_points":["服务范围","交付周期","定价方式"], "samples":[{"question":"Q1","platform":"DeepSeek","run":1,"answer":"原文回答……", "role":"independent|joint|citation_only|none", "sentiment":"positive|neutral|negative", "facts":"accurate|partial|wrong|unverifiable", "facts_found":["服务范围"],"as_of":"2026-09-19"}]} 口径：每题建议多轮（同一问题重复 7-8 次）；role 分级对应语义角色权重； 返回五大指标、语义角色加权分、逐题明细与「原文摘录」（便于客户自验）。 verify_citations=True 时会实测 AI 回答里引用的 URL 是否真的可访问（幻觉守卫）； extract_claims=True 时会把回答中的数字声明单独列出并标记为未核验。
| Name | Type | Req | Description |
|---|---|---|---|
| extract_claims | boolean | – | – |
| samples | string | yes | – |
| verify_citations | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the 中文 AI 可引用性（GEO/AEO）体检 MCP server?
中文 AI 可引用性（GEO/AEO）体检 is a hosted endpoint at https://savantcat.cn/mcp-geo, 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 · savantcat.cn
claude mcp add --transport http cn-savantcat-geo-cn 'https://savantcat.cn/mcp-geo'
What is the 中文 AI 可引用性（GEO/AEO）体检 MCP server?
中文 AI 可引用性（GEO/AEO）体检 is an MCP server listed in the public MCP registry as cn.savantcat/geo-cn. 中文站能否被豆包/DeepSeek/文心/Kimi 抓取、读懂、引用：可引用性审计、信源池占位探测、五大指标测量、修复计划、观测时序追踪. This page covers its hosted endpoint (https://savantcat.cn/mcp-geo).
Is the 中文 AI 可引用性（GEO/AEO）体检 MCP server safe to use?
中文 AI 可引用性（GEO/AEO）体检 scores 86 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 中文 AI 可引用性（GEO/AEO）体检 MCP server expose?
中文 AI 可引用性（GEO/AEO）体检 exposes 7 tools: audit_cn_citability, probe_source_pool, score_visibility, plan_fixes, query_history, and 2 more. Their descriptions and schemas cost roughly 1,328 tokens of context every time the server is loaded.
Does the 中文 AI 可引用性（GEO/AEO）体检 MCP server require authentication?
No. We connected to 中文 AI 可引用性（GEO/AEO）体检 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 中文 AI 可引用性（GEO/AEO）体检 MCP server still maintained?
中文 AI 可引用性（GEO/AEO）体检 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.