Lynnx Care: Guangzhou & Shenzhen hospital guide
REMOTE · TOUR.LYNNXAI.COM
Sourced, read-only hospital facts for Guangzhou and Shenzhen, with a free inquiry link.
Available components
Last scanned (8 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
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.
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.
- 29 Oct 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 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.
- 15 Oct 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.
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://tour.lynnxai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tour.lynnxai.com | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 23f58aa7d9bc380313793701087ad681 |
| SANs: tour.lynnxai.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tour.lynnxai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lynnxai.com. | 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 |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tour.lynnxai.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://tour.lynnxai.com/mcp | HTTPS enforced | 301 | https://tour.lynnxai.com/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. 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 →
ask_public_facts Ask about published hospital facts ~78
Read a sourced administrative answer from published hospital facts. Include only a public administrative question, not reports, passport numbers or personal medical details. This read-only tool does not create an inquiry, send email, book, upload or pay.
| Name | Type | Req | Description |
|---|---|---|---|
| facility_id | string | – | – |
| locale | string | – | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
get_facility Get hospital details ~34
Read a published institution and its sourced campus/channel facts. Internal booking fields are not exposed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
how_to_inquire How to send a free inquiry ~28
Describe the user's free plain-text inquiry option. This tool does not submit or send anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_guides List practical guides ~30
Read practical travel and hospital guides with examples from the same public directory.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
No output schema declared.
No examples provided.
prepare_inquiry_link Prepare a prefilled inquiry link ~132
Prepare a link to the free inquiry form, prefilled with a published institution (optionally its campus and service channel), city and an administrative topic. The link is for the user to open; the user writes the question, consents and verifies their email. This read-only tool does not submit an inquiry, send email, book, upload or pay, and accepts no personal details.
| Name | Type | Req | Description |
|---|---|---|---|
| campus_id | string | – | – |
| channel_id | string | – | – |
| city | string | – | – |
| facility_id | string | – | – |
| locale | string | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
search_facilities Search hospitals and clinics ~75
Search public hospital facts. Every condition must match the same campus and channel. Does not confirm clinical suitability or availability.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | – |
| city | string | – | – |
| has_price | boolean | – | – |
| q | string | – | – |
| scenario | string | – | – |
| service | string | – | – |
No output schema declared.
No examples provided.
How do I install the Lynnx Care: Guangzhou & Shenzhen hospital guide MCP server?
Lynnx Care: Guangzhou & Shenzhen hospital guide is a hosted endpoint at https://tour.lynnxai.com/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 · tour.lynnxai.com
claude mcp add --transport http com-lynnxai-lynnx-care 'https://tour.lynnxai.com/mcp'
What is the Lynnx Care: Guangzhou & Shenzhen hospital guide MCP server?
Lynnx Care: Guangzhou & Shenzhen hospital guide is an MCP server listed in the public MCP registry as com.lynnxai/lynnx-care. Sourced, read-only hospital facts for Guangzhou and Shenzhen, with a free inquiry link. This page covers its hosted endpoint (https://tour.lynnxai.com/mcp).
Is the Lynnx Care: Guangzhou & Shenzhen hospital guide MCP server safe to use?
Lynnx Care: Guangzhou & Shenzhen hospital guide scores 23 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 Lynnx Care: Guangzhou & Shenzhen hospital guide MCP server expose?
Lynnx Care: Guangzhou & Shenzhen hospital guide exposes 6 tools: search_facilities, get_facility, list_guides, how_to_inquire, ask_public_facts, prepare_inquiry_link. Their descriptions and schemas cost roughly 377 tokens of context every time the server is loaded.
Does the Lynnx Care: Guangzhou & Shenzhen hospital guide MCP server require authentication?
Its publisher declares no required credentials for Lynnx Care: Guangzhou & Shenzhen hospital guide. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Lynnx Care: Guangzhou & Shenzhen hospital guide MCP server still maintained?
Lynnx Care: Guangzhou & Shenzhen hospital guide 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.