WhyLingxi 保险顾问 Insurance Advisor
REMOTE · WHYLINGXI.CN · SCANNED AUG 3
保险产品搜索、推荐、保费试算、核保预检。覆盖65家保司483款产品。China insurance MCP server.
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 →
Endpoint Security57
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability43
- AI-judged instruction clarity (poor).Fail
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · whylingxi.cn
claude mcp add --transport http cn-whylingxi-insurance https://whylingxi.cn/mcp
[mcp_servers.cn-whylingxi-insurance] url = "https://whylingxi.cn/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cn-whylingxi-insurance": {
"type": "remote",
"url": "https://whylingxi.cn/mcp",
"enabled": true
}
}
} openclaw mcp add cn-whylingxi-insurance --url https://whylingxi.cn/mcp --transport streamable-http
mcp_servers:
cn-whylingxi-insurance:
url: "https://whylingxi.cn/mcp" {
"mcpServers": {
"cn-whylingxi-insurance": {
"type": "http",
"url": "https://whylingxi.cn/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.
- 2 Aug 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.
- 31 Jul 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
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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 Jul 26 52
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 3 Aug 2026 · Probed https://whylingxi.cn/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whylingxi.cn | CN=YR2,O=Let's Encrypt,C=US | 21 Jul 2026 | 19 Oct 2026 | RSA 2048 | SHA256-RSA | 5afcf70c29744ec68b871cfe88f73058eb6 |
| SANs: whylingxi.cn | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of whylingxi.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | present | 33094 | 8 | Verified |
| whylingxi.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whylingxi.cn/mcp | Verified | 200 | |
| http (plaintext) | http://whylingxi.cn/mcp | HTTPS enforced | 301 | https://whylingxi.cn/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.
answer_question ~86
回答保险知识问题。默认返回知识库检索结果；传synthesize:true可获得LLM整合答案。
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | — | （可选）针对某款产品的问题 |
| question | string | yes | 问题 |
| synthesize | boolean | — | 是否调LLM整合答案（默认false，纯检索模式更快） |
No output schema declared.
No examples provided.
chat ~66
自然语言多轮对话（适合信息不确定、需要引导的场景，或人类用户直接使用）。
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | 用户消息 |
| session_id | string | — | 会话ID，传入可保持多轮对话上下文 |
No output schema declared.
No examples provided.
check_underwriting ~155
核保预判：根据用户健康状况，评估各产品的可投保性（可正常投保/需加费除外/可能拒保）。
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | — | 年龄（影响可选产品范围） |
| category | string | — | 想投保的险种（不传则评估医疗+重疾+意外+定寿） |
| health_conditions | array | yes | 健康状况列表，如["高血压2级","甲状腺结节3类","乙肝小三阳"] |
| product_ids | array | — | 指定产品ID列表（不传则自动选取各险种Top产品评估） |
No output schema declared.
No examples provided.
compare_products ~87
对比2-5款产品的关键维度（保费、保障、免赔额、续保等），返回结构化对比表。
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | — | 用于查询精确保费的年龄 |
| gender | string | — | 用于查询精确保费的性别 |
| product_ids | array | yes | 产品ID列表（2-5个） |
No output schema declared.
No examples provided.
get_premium ~52
查询指定产品在特定年龄/性别下的精确保费数据。
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | yes | 年龄 |
| gender | string | — | — |
| product_id | integer | yes | 产品ID |
No output schema declared.
No examples provided.
get_product_detail ~80
获取单个产品的结构化信息。compact=true时只返回摘要字段，适合Agent快速浏览；默认返回完整信息含条款详情。
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | 精简模式：只返回核心字段+coverage前8项摘要，省略条款/FAQ详情 |
| product_id | integer | yes | 产品ID |
No output schema declared.
No examples provided.
get_schema ~107
获取调用策略和字段优先级。调用流程：(1)收集用户age后即可调recommend(2)有health_conditions时自动附带核保结论(3)include_reasoning默认false,Agent自行组织语言(4)返回的source_url可直接给用户作为投保链接。本工具返回各能力的字段优先级、缺失影响、默认行为。
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | — | 想了解哪个能力，不传则返回全部 |
No output schema declared.
No examples provided.
recommend ~243
根据用户画像推荐保险方案（核心工具）。信息不全也可调用——返回最佳推荐+缺失字段提示。传入health_conditions自动附带核保结论。默认纯数据模式(<100ms)，设include_reasoning:true生成自然语言理由(+3s)。
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | yes | 年龄（必填） |
| budget | number | — | 年预算（元） |
| existing_coverage | array | — | 已有保障，如["百万医疗","意外险"] |
| family_role | string | — | 被保人角色 |
| gender | string | — | — |
| has_social_security | boolean | — | 是否有社保 |
| health_conditions | array | — | 既往症，如["高血压2级","甲状腺结节"] |
| include_reasoning | boolean | — | 是否生成LLM推荐理由（默认false，Agent调用无需开启；设true适用于直接面向人类展示） |
| needs | array | — | 需求列表，如["重疾保障","医疗报销","意外防护"] |
| occupation_class | integer | — | 职业类别(1-6类) |
No output schema declared.
No examples provided.
search_products ~127
按条件搜索保险产品，返回结构化JSON列表。支持按险种、年龄、预算、关键词筛选。
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | — | 被保险人年龄 |
| budget | number | — | 年预算上限（元） |
| category | string | — | 险种：医疗险/重疾险/意外险/定期寿险/终身寿险/年金险/旅游险/团险 |
| keyword | string | — | 产品名或保险公司关键词 |
| limit | integer | — | 最多返回条数，默认10 |
No output schema declared.
No examples provided.