# 好啦体检 MCP (remote · ai.ihaola.com.cn)

企业团检分档报价与企业咨询、个人体检方案推荐、门店查询、体检预约、订单与体检件查询、体检常见问题。合作体检机构 800+ 门店，覆盖 240+ 城市，其中 540+ 门店支持 AI 直接查询与预约。

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ai.ihaola.com.cn`: 61/100 (this document), [markdown](https://verifymcp.io/servers/cn-com-ihaola-health-checkup-planner/api-mcp-haola-pe.md), [page](https://verifymcp.io/servers/cn-com-ihaola-health-checkup-planner/api-mcp-haola-pe)

## Channel facts

- Endpoint: `https://ai.ihaola.com.cn/api/mcp/haola-pe`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-05.

- **Endpoint Security**: 57/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 26 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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4999 tokens (~192/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the 好啦体检 MCP server?

好啦体检 MCP is a hosted endpoint at https://ai.ihaola.com.cn/api/mcp/haola-pe, 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 cn-com-ihaola-health-checkup-planner 'https://ai.ihaola.com.cn/api/mcp/haola-pe'
```

### Cursor

```json
{
  "mcpServers": {
    "cn-com-ihaola-health-checkup-planner": {
      "url": "https://ai.ihaola.com.cn/api/mcp/haola-pe"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cn-com-ihaola-health-checkup-planner": {
      "type": "http",
      "url": "https://ai.ihaola.com.cn/api/mcp/haola-pe"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cn-com-ihaola-health-checkup-planner]
url = "https://ai.ihaola.com.cn/api/mcp/haola-pe"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cn-com-ihaola-health-checkup-planner": {
      "type": "remote",
      "url": "https://ai.ihaola.com.cn/api/mcp/haola-pe",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cn-com-ihaola-health-checkup-planner --url 'https://ai.ihaola.com.cn/api/mcp/haola-pe' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cn-com-ihaola-health-checkup-planner:
    url: "https://ai.ihaola.com.cn/api/mcp/haola-pe"
```

### Netclaw

```json
{
  "McpServers": {
    "cn-com-ihaola-health-checkup-planner": {
      "Transport": "http",
      "Url": "https://ai.ihaola.com.cn/api/mcp/haola-pe"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cn-com-ihaola-health-checkup-planner -t streamable-http -u 'https://ai.ihaola.com.cn/api/mcp/haola-pe'
```

### Other

```json
{
  "mcpServers": {
    "cn-com-ihaola-health-checkup-planner": {
      "type": "http",
      "url": "https://ai.ihaola.com.cn/api/mcp/haola-pe"
    }
  }
}
```

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-11-05 (score 61, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] New tool “contact_profile_correct”

### 2026-11-04 (score 60, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “reservation_book” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 168 → 190
- [cosmetic] “reservation_book” added an optional parameter “birthday”
- [cosmetic] “reservation_book” added an optional parameter “consent”
- [cosmetic] “reservation_book” added an optional parameter “consentText”
- [cosmetic] “reservation_book” added an optional parameter “contactDraftId”
- [cosmetic] “reservation_book” added an optional parameter “contactMethod”
- [cosmetic] “reservation_book” added an optional parameter “customerID”
- [cosmetic] “reservation_book” added an optional parameter “customerMobile”
- [cosmetic] “reservation_book” added an optional parameter “customerName”
- [cosmetic] “reservation_book” added an optional parameter “gender”
- [cosmetic] “reservation_book” added an optional parameter “marital”
- [cosmetic] “reservation_book” added an optional parameter “relation”

### 2026-11-03 (score 60, 0)

- [security regression] HSTS header: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “contact_get” rewrote its description, which is the text the model reads
- [security] Tool “contact_update” rewrote its description, which is the text the model reads
- [security] Tool “reservation_book” rewrote its description, which is the text the model reads
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-02 (score 60, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-01 (score 60, +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.

### 2026-10-31 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 59)

First indexed and scored.

## MCP tools (26)

### `vendor_list` (~175 tokens)

vendor.list

[匿名可调用] 查门店地址。支持三种方式，至少传一种：1) hospitalCode（可带 vendorids，按第一个品牌查）；2) longitude+latitude（可带 radius 米，默认 50000，可带 vendorids）；3) province/city/district（可带 vendorids）。外部调用仅支持 health100/haolaruici，partnerid 仅内部可用。不确定品牌和覆盖城市时先用 vendor.brands。本体: vendor → Action: list

Input parameters:

- `city` (string)
- `district` (string)
- `hospitalCode` (string)
- `latitude` (number)
- `longitude` (number)
- `province` (string)
- `radius` (number)
- `vendorids` (array)

### `vendor_brands` (~42 tokens)

vendor.brands

[匿名可调用] 查各体检品牌覆盖的城市（品牌聚合摘要，不返回具体门店）。本体: vendor → Action: brands

### `order_list` (~130 tokens)

order.list

[需要登录] 查订单。查询 userOrders 集合。调用方归属甲方由服务端身份解析，filter 中无需传 partnerid。支持 $gte/$lte 日期范围、$in/$or 多值匹配。本体: order → Action: list

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `filter` (object)
- `limit` (number)
- `page` (number)

### `welfare_list` (~168 tokens)

welfare.list

[需要登录] 查用户体检件。查询 userWelfare 集合。传 {customerMobile: "138xxx"} 或 {name: "张三"} 查对应用户的体检件。已知 userid 可直接传 {userid: "xxx"}。本体: welfare → Action: list

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `ID` (string)
- `mobile` (string)
- `name` (string)
- `partnerid` (string)
- `rootid` (string)
- `serviceid` (string)
- `userid` (string)

### `corp_inquiry` (~106 tokens)

corp.inquiry

[匿名可调用] 提交企业商务咨询。企业客户有任何问题（合作咨询、产品了解、报价请求、投诉建议）均可提交，销售 24h 内联系。本体: corp → Action: inquiry

Input parameters:

- `budget` (string)
- `city` (string)
- `company` (string, required)
- `contact` (string, required)
- `employees` (number)
- `message` (string)
- `phone` (string, required)

### `corp_contact` (~60 tokens)

corp.contact

[匿名可调用] 查询好啦商务对接人（团检/商务合作）：返回对接人姓名、电话、邮箱、二维码图片 URL。用户报价后需要人工商务对接时调用。本体: corp → Action: contact

### `plan_quotation` (~309 tokens)

plan.quotation

[匿名可调用] 企业团检报价：quotes 为对象数组，每档一个方案。每项 = { tier(档名，仅标识该档、不参与报价，返回时回填), budget(人均预算元，必填), healthConcerns(该档健康诉求，必填), populations?(人群数组 man/lady/girl，默认三人，该档) }。可选 partnerId（甲方 UUID），透传给 /plan/quotation 按伙伴定价。返回 data.list（每档 { tier, budget, planList, combinedPrice, discount }），其中 planList 为**按人群的数组**（每项 { population, price, items, planId }），逐档按人群拆分并发取值；planId 是该档该人群的方案标识，体检预约时传给 reservation.book，不要自己拼项目；discount 为该伙伴折数（如 5 表示 5 折，无则 null）。调用前先用 knowledge_get({uri:"objects/checkup-proposal"}) 加载《企业团检方案顾问》引导词作为 agent 的 system prompt；对客话术与输出模板必须遵循该引导词，严禁编造项目/费用。字段说明见 knowledge://objects/checkup-proposal。本体: plan → Action: quotation

Input parameters:

- `partnerId` (string)
- `quotes` (array, required)

### `plan_recommend` (~221 tokens)

plan.recommend

[需要登录] 个人体检推荐：按调用方身份读用户名下体检件与模板，结合性别、婚姻状况、预算、健康诉求推荐体检项目，返回 data.selected_items（每项带 constraintId）与 planId。planId 直接传给 reservation.book 预约，不要自己拼项目。长耗时，建议每阶段调用 progress.report。本体: plan → Action: recommend

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `age` (number)
- `budget` (number)
- `gender` (string, required)
- `mainComplaint` (string)
- `marital` (string)
- `modification` (string)
- `previousPackage` (array)
- `reportHistory` (string)
- `userContext` (string)
- `welfareid` (string)

### `faq` (~64 tokens)

[匿名可调用] 体检 FAQ。不传 query 则列出所有问题。query 必须是短关键词(2-4字，如"报告"、"预约"、"空腹")，不要传完整问句。

Input parameters:

- `query` (string)

### `knowledge_get` (~135 tokens)

knowledge.get

[匿名可调用] 按需查询领域知识。外部可用 URI: enums(状态码) / objects/contact(联系人) / objects/contact-profile(健康画像) / objects/checkup-proposal(企业团检方案顾问引导词)。查 action 参数用 help()。团检报价场景先用 knowledge_get({uri:"objects/checkup-proposal"}) 加载《企业团检方案顾问》引导词作为外部 MCP agent 的 system prompt，再调 plan_quotation；报价话术与输出模板必须遵循该引导词

Input parameters:

- `uri` (string)

### `help` (~71 tokens)

[匿名可调用] 三级帮助系统。无参列出本体；传 ontology 列出该本体下工具；传 ontology 和 sub_action 查看参数，sub_action 用完整名称，如 vendor.list、plan.quotation。

Input parameters:

- `ontology` (string)
- `sub_action` (string)

### `welfare_detail` (~99 tokens)

welfare.detail

[需要登录] 查询指定福利的详细内容，包括检查项目列表、规则说明、适用机构等。本体: welfare → Action: detail

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `vendorid` (string)
- `welfareid` (string, required)

### `cautions` (~161 tokens)

[需要登录] 根据体检项目查询注意事项（饮食、用药、禁忌等）。需调用方用户标识（external_user_id 自动注入），partnerid 由服务端按用户标识解析，禁止客户端传。传 checkPackage 查套餐注意事项（必带 vendorid）；传 serviceid 仅允许查本人订单。本体: knowledge → Action: cautions

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `checkPackage` (object)
- `serviceid` (string)
- `vendorid` (string)

### `order_detail` (~91 tokens)

order.detail

[需要登录] 查询单个订单完整详情，包括预约信息、医院信息、套餐项目、支付状态。本体: order → Action: detail

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `serviceid` (string, required)

### `contact_list` (~123 tokens)

contact.list

[需要登录] 按 relation/gender 查询当前用户的联系人。用户提到家人时必须先调用；唯一候选可直接使用 contactid，多个候选请用户选择，未选定时禁止保存画像。本体: contact → Action: list

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `gender` (string)
- `relation` (string)

### `contact_get` (~96 tokens)

contact.get

[需要登录] 查询指定体检人的完整信息（含脱敏证件号）。本体: contact → Action: get

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `contactId` (string)
- `contactid` (string)

### `contact_create` (~152 tokens)

contact.create

[需要登录] 创建家属临时联系人。relation 必填，self 由系统创建；姓名、手机号、证件号可后补。本体: contact → Action: create

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `IDType` (string)
- `birthday` (string)
- `customerID` (string)
- `customerMobile` (string)
- `customerName` (string)
- `gender` (string)
- `marital` (string)
- `relation` (string, required)

### `contact_update` (~145 tokens)

contact.update

[需要登录] 更新体检人信息（姓名、手机号等）。本体: contact → Action: update

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `IDType` (string)
- `birthday` (string)
- `contactId` (string)
- `contactid` (string)
- `customerID` (string)
- `customerMobile` (string)
- `customerName` (string)
- `gender` (string)
- `marital` (string)

### `contact_profile_get` (~103 tokens)

contact.profile.get

[需要登录] 按 contactid 查询联系人的结构化健康画像。不传 contactid 时读取当前用户本人。本体: contact → Action: profile.get

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `contactId` (string)
- `contactid` (string)

### `contact_profile_save` (~212 tokens)

contact.profile.save

[需要登录] 仅在用户明确要求保存或更新长期健康画像时调用；仅推荐方案不得调用。本人不传 contactid，家人必须先解析唯一 contactid，禁止把家人信息写入本人档案。返回更新后的完整画像与 created。本体: contact → Action: profile.save

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `allergy_intolerance` (object)
- `contactId` (string)
- `contactid` (string)
- `demographics` (object)
- `examinations` (array)
- `family_history` (array)
- `lifestyle` (object)
- `measurements` (array)
- `medications` (array)
- `preferences_constraints` (object)
- `problem_list` (array)
- `surgeries` (array)

### `contact_profile_correct` (~174 tokens)

contact.profile.correct

[需要登录] 纠正联系人健康画像中的错误记录。只删除时 contactid 指定源联系人，本人不传；迁移时额外传 targetContactid。entries.path 指定模块或子字段，entries.match 指定必须唯一命中的字段。匹配不到或多条命中都会失败，不修改数据。本体: contact → Action: profile.correct

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `contactId` (string)
- `contactid` (string)
- `entries` (array, required)
- `targetContactId` (string)
- `targetContactid` (string)

### `reservation_book` (~807 tokens)

reservation.book

[需要登录] 体检预约：按 planId 取出项目，交给伙伴接口下单。传 contactId 时直接使用该体检人。没有 contactId 时，支持 elicitation form 的客户端先展示全部常用体检人和新建入口；选择完整联系人后直接进入协议授权，选择信息不完整的联系人时返回第二段补全表单并更新原联系人，选择新建时返回第二段表单填写姓名、手机号、与本人关系、证件类型、证件号、出生日期、性别、婚否和授权。出生日期和性别仅在非身份证时必填，服务端在提交后校验，提交后保存为常用体检人。不支持 elicitation form 的客户端返回 contactMethodRequired，用户可以选择在对话中填写或打开 H5 体检人页面，不强制跳转。选择在对话中填写后返回 contactRequired，包含待填字段和 contactDraftId；Agent 按字段逐项询问，每次只问一项，用户确认后把各字段、contactDraftId 和 consent=true 一起传回，服务端校验并保存联系人后继续预约。证件号会出现在当前对话中，可能被客户端记录；该隐私提示只向用户提示一次，提交后 Agent 不复述、不回显证件号，只引用 contactId。选择 H5 后返回 contactEntryUrl，用户添加体检人后调用 contact_list 获取 contactId，再继续预约。不要主动要求用户发送身份证号；用户已选择在对话中填写时，可以继续询问证件号。IDType 为 SFZ 时按身份证规则校验。体检项目只来自 planId，客户端不能提交项目。预约前会通过 input_required 展示本次需要的动态协议；非表单客户端返回 consentRequired，用户确认后把确认话术原文作为 consentText 传入。返回 contactId、serviceid 和 orderEntryUrl；保存联系人时同时返回 contactid 和 contactSaved，contactSaved=false 表示预约已成功但联系人保存失败。用户在 H5 用手机号登录后可看到自己的订单，并可支付、改期/取消、查看检前注意事项、查看体检报告。渠道需要用户支付时返回支付链接 payUrl 和支付提示；客户端支持 elicitation URL 时，服务端通过 URL 模式打开 payUrl，最终结果仍返回 orderEntryUrl，客户端不支持时直接返回 payUrl 和 orderEntryUrl。客户端可使用 payUrl 生成二维码展示给用户。payUrl 有效期为订单创建后 30 分钟。重复预约命中已有未支付订单时，返回原 serviceid 和该订单的 payUrl。status 表示支付状态，预约状态以 rsvStatus 为准。本体: reservation → Action: book

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `IDType` (string)
- `appointmentDate` (string, required)
- `birthday` (string)
- `consent` (boolean)
- `consentText` (string)
- `contactDraftId` (string)
- `contactId` (string)
- `contactMethod` (string)
- `contactid` (string)
- `customerID` (string)
- `customerMobile` (string)
- `customerName` (string)
- `gender` (string)
- `hospitalCode` (string, required)
- `marital` (string)
- `payType` (string)
- `planId` (string, required)
- `relation` (string)
- `timespan` (string)
- `vendorid` (string, required)

### `reservation_cancel` (~101 tokens)

reservation.cancel

[需要登录] 取消预约：按预约号取消；已支付订单会同时发起退款。预约号取自 reservation.book 返回的 serviceid。本体: reservation → Action: cancel

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `reservationId` (string, required)

### `reservation_modify` (~91 tokens)

reservation.modify

[需要登录] 更改预约日期：按预约号改期。本体: reservation → Action: modify

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `appointmentDate` (string, required)
- `reservationId` (string, required)

### `card_list` (~108 tokens)

card.list

[需要登录] 根据卡号查卡密及兑换使用情况。welfareId 为空=未兑换，非空时串联福利和订单。本体: card → Action: list

鉴权：需要用户登录令牌，或已经绑定用户的云市场实例凭证。未登录调用返回 401；云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

Input parameters:

- `cardId` (string, required)
- `limit` (number)

### `progress_report` (~83 tokens)

progress.report

[匿名可调用] 长耗时任务进度上报。agent 每完成一个阶段调用一次，text 为给用户看的可读进度，如「报告解析中，预计 10 秒」。不落地业务数据，仅用于向用户展示过程。

Input parameters:

- `percent` (number)
- `stage` (string)
- `text` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cn-com-ihaola-health-checkup-planner/api-mcp-haola-pe#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 60
- 2026-11-03: 60
- 2026-11-02: 60
- 2026-11-01: 60
- 2026-10-31: 59
- 2026-10-30: 59

## Common questions

### What is the 好啦体检 MCP server?

好啦体检 MCP is listed in the public MCP registry as cn.com.ihaola/health-checkup-planner. 企业团检分档报价与企业咨询、个人体检方案推荐、门店查询、体检预约、订单与体检件查询、体检常见问题。合作体检机构 800+ 门店，覆盖 240+ 城市，其中 540+ 门店支持 AI 直接查询与预约。 This page covers its hosted endpoint (https://ai.ihaola.com.cn/api/mcp/haola-pe).

### Is the 好啦体检 MCP server safe to use?

好啦体检 MCP scores 61 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 好啦体检 MCP server expose?

好啦体检 MCP exposes 26 tools: vendor_list, vendor_brands, order_list, welfare_list, corp_inquiry, and 21 more. Their descriptions and schemas cost roughly 4,027 tokens of context every time the server is loaded.

### Does the 好啦体检 MCP server require authentication?

No. We connected to 好啦体检 MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 好啦体检 MCP server still maintained?

好啦体检 MCP 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.

### What did VerifyMCP test on the 好啦体检 MCP server?

VerifyMCP ran 12 checks on 好啦体检 MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about 好啦体检 MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ai.ihaola.com.cn/api/mcp/haola-pe
- Website: https://www.ihaola.com.cn/
- Changelog RSS feed: https://verifymcp.io/servers/cn-com-ihaola-health-checkup-planner/api-mcp-haola-pe.xml
- Changelog JSON feed: https://verifymcp.io/servers/cn-com-ihaola-health-checkup-planner/api-mcp-haola-pe/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cn-com-ihaola-health-checkup-planner/api-mcp-haola-pe.json
- HTML version of this page: https://verifymcp.io/servers/cn-com-ihaola-health-checkup-planner/api-mcp-haola-pe