Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WhyLingxi 保险顾问 Insurance Advisor

REMOTE · WHYLINGXI.CN · SCANNED SEP 25

保险产品搜索、推荐、保费试算、核保预检。覆盖65家保司483款产品。China insurance MCP server.

Available components

0 this week 76 Trust /100
Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the WhyLingxi 保险顾问 Insurance Advisor MCP server?

WhyLingxi 保险顾问 Insurance Advisor is a hosted endpoint at https://whylingxi.cn/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 · whylingxi.cn

# add to Claude Code
claude mcp add --transport http cn-whylingxi-insurance 'https://whylingxi.cn/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cn-whylingxi-insurance": {
      "url": "https://whylingxi.cn/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cn-whylingxi-insurance": {
      "type": "http",
      "url": "https://whylingxi.cn/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cn-whylingxi-insurance]
url = "https://whylingxi.cn/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cn-whylingxi-insurance": {
      "type": "remote",
      "url": "https://whylingxi.cn/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cn-whylingxi-insurance --url 'https://whylingxi.cn/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cn-whylingxi-insurance:
    url: "https://whylingxi.cn/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cn-whylingxi-insurance": {
      "Transport": "http",
      "Url": "https://whylingxi.cn/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cn-whylingxi-insurance -t streamable-http -u 'https://whylingxi.cn/mcp'
// mcp.json
{
  "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.

Changelog

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.

  • 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 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
  • 31 Jul 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
  • 27 Jul 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
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 25 Sept 2026 · Probed https://whylingxi.cn/mcp

TLS unreached
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 Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://whylingxi.cn/mcp Unreachable
http (plaintext) http://whylingxi.cn/mcp HTTPS enforced
MCP tools · 9 exposed · ~1,003 tokens

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 →

Tool Tokens
answer_question ~86

回答保险知识问题。默认返回知识库检索结果;传synthesize:true可获得LLM整合答案。

NameTypeReqDescription
product_idinteger–(可选)针对某款产品的问题
questionstringyes问题
synthesizeboolean–是否调LLM整合答案(默认false,纯检索模式更快)

No output schema declared.

No examples provided.

chat ~66

自然语言多轮对话(适合信息不确定、需要引导的场景,或人类用户直接使用)。

NameTypeReqDescription
messagestringyes用户消息
session_idstring–会话ID,传入可保持多轮对话上下文

No output schema declared.

No examples provided.

check_underwriting ~155

核保预判:根据用户健康状况,评估各产品的可投保性(可正常投保/需加费除外/可能拒保)。

NameTypeReqDescription
ageinteger–年龄(影响可选产品范围)
categorystring–想投保的险种(不传则评估医疗+重疾+意外+定寿)
health_conditionsarrayyes健康状况列表,如["高血压2级","甲状腺结节3类","乙肝小三阳"]
product_idsarray–指定产品ID列表(不传则自动选取各险种Top产品评估)

No output schema declared.

No examples provided.

compare_products ~87

对比2-5款产品的关键维度(保费、保障、免赔额、续保等),返回结构化对比表。

NameTypeReqDescription
ageinteger–用于查询精确保费的年龄
genderstring–用于查询精确保费的性别
product_idsarrayyes产品ID列表(2-5个)

No output schema declared.

No examples provided.

get_premium ~52

查询指定产品在特定年龄/性别下的精确保费数据。

NameTypeReqDescription
ageintegeryes年龄
genderstring––
product_idintegeryes产品ID

No output schema declared.

No examples provided.

get_product_detail ~80

获取单个产品的结构化信息。compact=true时只返回摘要字段,适合Agent快速浏览;默认返回完整信息含条款详情。

NameTypeReqDescription
compactboolean–精简模式:只返回核心字段+coverage前8项摘要,省略条款/FAQ详情
product_idintegeryes产品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可直接给用户作为投保链接。本工具返回各能力的字段优先级、缺失影响、默认行为。

NameTypeReqDescription
capabilitystring–想了解哪个能力,不传则返回全部

No output schema declared.

No examples provided.

recommend ~243

根据用户画像推荐保险方案(核心工具)。信息不全也可调用——返回最佳推荐+缺失字段提示。传入health_conditions自动附带核保结论。默认纯数据模式(<100ms),设include_reasoning:true生成自然语言理由(+3s)。

NameTypeReqDescription
ageintegeryes年龄(必填)
budgetnumber–年预算(元)
existing_coveragearray–已有保障,如["百万医疗","意外险"]
family_rolestring–被保人角色
genderstring––
has_social_securityboolean–是否有社保
health_conditionsarray–既往症,如["高血压2级","甲状腺结节"]
include_reasoningboolean–是否生成LLM推荐理由(默认false,Agent调用无需开启;设true适用于直接面向人类展示)
needsarray–需求列表,如["重疾保障","医疗报销","意外防护"]
occupation_classinteger–职业类别(1-6类)

No output schema declared.

No examples provided.

search_products ~127

按条件搜索保险产品,返回结构化JSON列表。支持按险种、年龄、预算、关键词筛选。

NameTypeReqDescription
ageinteger–被保险人年龄
budgetnumber–年预算上限(元)
categorystring–险种:医疗险/重疾险/意外险/定期寿险/终身寿险/年金险/旅游险/团险
keywordstring–产品名或保险公司关键词
limitinteger–最多返回条数,默认10

No output schema declared.

No examples provided.

Common questions

What is the WhyLingxi 保险顾问 Insurance Advisor MCP server?

WhyLingxi 保险顾问 Insurance Advisor is an MCP server listed in the public MCP registry as cn.whylingxi/insurance. 保险产品搜索、推荐、保费试算、核保预检。覆盖65家保司483款产品。China insurance MCP server. This page covers its hosted endpoint (https://whylingxi.cn/mcp).

Is the WhyLingxi 保险顾问 Insurance Advisor MCP server safe to use?

WhyLingxi 保险顾问 Insurance Advisor scores 76 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 WhyLingxi 保险顾问 Insurance Advisor MCP server expose?

WhyLingxi 保险顾问 Insurance Advisor exposes 9 tools: get_schema, search_products, get_product_detail, compare_products, recommend, and 4 more. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.

Does the WhyLingxi 保险顾问 Insurance Advisor MCP server require authentication?

Its publisher declares no required credentials for WhyLingxi 保险顾问 Insurance Advisor. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the WhyLingxi 保险顾问 Insurance Advisor MCP server still maintained?

WhyLingxi 保险顾问 Insurance Advisor is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.