mcp-registry/cn.com.ihaola/haola-pe · v1.0.0
As of 2026-10-26 20:01 UTC, the Com Ihaola Haola Pe MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 2 minutes.
企业团检分档方案、门店查询、体检 FAQ 与企业咨询,覆盖 241 城。
Point your MCP client at this streamable-http endpoint: https://ai.ihaola.com.cn/api/mcp/haola-pe
23 of 23 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
83 parameter(s) across 21 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Reachable 98.6% of the time over the last 30 days; median recovery 2 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
In the last 30 days: 3 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 21 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcn.com.ihaola%2Fhaola-pe/fixes
{
"name": "card_list",
"description": "根据卡号查卡密及兑换使用情况。welfareId 为空=未兑换,非空时串联福利和订单。本体: card → Action: list\n\n鉴权:需要用户登录令牌,或已经绑定用户的云市场实例凭证。未登录调用返回 401;云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"cardId"
],
"properties": {
"limit": {
"type": "number"
},
"cardId": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "card.list"
}{
"name": "contact_create",
"description": "新增就诊人信息。本体: contact → Action: create\n\n鉴权:需要用户登录令牌,或已经绑定用户的云市场实例凭证。未登录调用返回 401;云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"customerName",
"customerMobile",
"customerID"
],
"properties": {
"IDType": {
"type": "string"
},
"gender": {
"type": "string"
},
"birthday": {
"type": "string"
},
"marriage": {
"type": "string"
},
"relation": {
"type": "string"
},
"customerID": {
"type": "string"
},
"customerName": {
"type": "string"
},
"customerMobile": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "contact.create"
}{
"name": "contact_get",
"description": "查询指定就诊人的完整信息(含脱敏证件号)。本体: contact → Action: get\n\n鉴权:需要用户登录令牌,或已经绑定用户的云市场实例凭证。未登录调用返回 401;云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"contactid"
],
"properties": {
"userid": {
"type": "string"
},
"contactid": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "contact.get"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cn.com.ihaola/haola-pe"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/cn.com.ihaola/haola-pe"}) over MCP.
reservation_book ~292 tokensplan_recommend ~231 tokensplan_quotation ~225 tokensvendor_list ~180 tokenscontact_create ~156 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcn.com.ihaola%2Fhaola-pe?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcn.com.ihaola%2Fhaola-pe?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcn.com.ihaola%2Fhaola-pe.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcn.com.ihaola%2Fhaola-pe.svg :target: https://glimind.com/server/mcp-registry%2Fcn.com.ihaola%2Fhaola-pe?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ed76cd47ba220919…, first seen 2026-10-26, included at leaf 71164 of 75,178. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable other servers · most reliable database servers · most reliable contact servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 20:01 UTC, the Com Ihaola Haola Pe MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 2 minutes.
Com Ihaola Haola Pe MCP server advertises 23 tools, including card_list, cautions, contact_create, contact_get, contact_list.
Point your MCP client at this streamable-http endpoint: https://ai.ihaola.com.cn/api/mcp/haola-pe
Glimind scanned all 23 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.