io.github.erxianzhuangzu/lian-chain-intelligence
REMOTE · LIAN.YISUNCLOUD.COM
Query tech-industry-market chain transmission and entity status.
Available components
Last scanned (2 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Data and Analytics
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability59
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1848 tokens (~115/item across 16 items; 16 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Tool “intel_availability” rewrote its description, which is the text the model reads security
- Tool “intel_brief” rewrote its description, which is the text the model reads security
- Tool “intel_category” rewrote its description, which is the text the model reads security
- Tool “intel_category_demand_pull” rewrote its description, which is the text the model reads security
- Tool “intel_category_migration” rewrote its description, which is the text the model reads security
- Tool “intel_category_opportunity” rewrote its description, which is the text the model reads security
- Tool “intel_category_supply” rewrote its description, which is the text the model reads security
- Tool “intel_chain” rewrote its description, which is the text the model reads security
- Tool “intel_chain_master” rewrote its description, which is the text the model reads security
- Tool “intel_demand” rewrote its description, which is the text the model reads security
- Tool “intel_global_race” rewrote its description, which is the text the model reads security
- Tool “intel_heal” rewrote its description, which is the text the model reads security
- Tool “intel_signal” rewrote its description, which is the text the model reads security
- Tool “intel_tech_daily” rewrote its description, which is the text the model reads security
- Tool “intel_tech_launch” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.5.1 → 1.6.0 functional
- New tool “intel_tech_dir” functional
- “intel_global_race” added an optional parameter “category” cosmetic
- “intel_global_race” added an optional parameter “slug” cosmetic
- “intel_tech_launch” added an optional parameter “slug” cosmetic
- “intel_tech_launch” reworded the description of “category” cosmetic
- “intel_global_race” dropped the optional parameter “date” cosmetic
- “intel_tech_launch” dropped the optional parameter “date” cosmetic
- 26 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.
- 24 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.
- 22 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.
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://lian.yisuncloud.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lian.yisuncloud.com | CN=YR1,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 5adef1947c5e6f07bdeb73259f469eb2ebf |
| SANs: lian.yisuncloud.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lian.yisuncloud.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| yisuncloud.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lian.yisuncloud.com/mcp | Verified | 200 | |
| http (plaintext) | http://lian.yisuncloud.com/mcp | HTTPS enforced | 301 | https://lian.yisuncloud.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 →
intel_availability ~99
[v1.6.0] 先查：available_now、coverage、requires_trigger。建议再调 chain/signal/brief。Check coverage status first: available_now, coverage, requires_trigger. Then chain/signal/brief.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | 实体名，如 OpenAI、华为、台积电 |
| entity_id | string | – | 如 ent_openai；与 entity 二选一或并用 |
No output schema declared.
No examples provided.
intel_brief ~140
[v1.6.0] 规则模板拼的缺口组合：落地、商业化、技术，以及链主、跨境，哪几条在。不是大模型。Template of which gap combination is present. Not an LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | 实体名，如 OpenAI、华为、台积电 |
| entity_id | string | – | 如 ent_openai；与 entity 二选一或并用 |
| heal | string | – | 传 0 可跳过愈合快照写入 |
| window | number | – | 近窗天数 7–90 |
No output schema declared.
No examples provided.
intel_category ~85
[v1.6.0] 品类全包（肥）。优先用原子工具降 token：intel_category_opportunity / _supply / _demand_pull / _migration。Full category pack. Prefer atomic siblings to cut tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Alias of slug |
| slug | string | – | Category slug, e.g. optical_module |
No output schema declared.
No examples provided.
intel_category_demand_pull ~67
[v1.6.0] L-153a 原子：只出需求倒逼段（signals/chains），公开无 chains。Atomic: demand_pull slice only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Alias of slug |
| slug | string | – | Category slug |
No output schema declared.
No examples provided.
intel_category_migration ~82
[v1.6.0] L-153a 原子：技术迁移层。非壁垒仅标题示意/锁定；全量需壁垒。Atomic: tech_migration. Non-pro: teaser/locked only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Alias of slug |
| slug | string | – | Category slug |
No output schema declared.
No examples provided.
intel_category_opportunity ~79
[v1.6.0] L-153a 原子：只出品类机会面（海外/价差/切入点等），已按档裁剪。Atomic: opportunity slice only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Alias of slug |
| slug | string | – | Category slug, e.g. optical_module |
No output schema declared.
No examples provided.
intel_category_supply ~71
[v1.6.0] L-153a 原子：只出品类供给（整机/零部件示意），已按档裁剪。Atomic: supply slice only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Alias of slug |
| slug | string | – | Category slug |
No output schema declared.
No examples provided.
intel_chain ~89
[v1.6.0] 全链：timeline、delta_days、vs_prior（≈get_chain）。需 Key。Full chain: timeline, delta_days, vs_prior. Requires key.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | 实体名，如 OpenAI、华为、台积电 |
| entity_id | string | – | 如 ent_openai；与 entity 二选一或并用 |
No output schema declared.
No examples provided.
intel_chain_master ~103
[v1.6.0] 已发布的链主倒逼。承接方不是定点供应商。公开/免费档不给来源 URL。Published chain-master push. Public/free tiers hide source URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, e.g. robot_joint |
| entity | string | – | Chain-master name or slug, e.g. 特斯拉 |
| entity_id | string | – | e.g. ent_tesla |
No output schema declared.
No examples provided.
intel_demand ~124
[v1.6.0] 需求倒逼（品类匿名 signals/chains）。list=1 列实体；或传 entity/slug。公开前 3 条 signal、无 chains。Demand-pull. list=1 or entity. Public: 3 signals, no chains.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | 品类 slug/id，如 portable_power |
| entity_id | string | – | Alias of entity |
| list | boolean | – | true=只列有需求倒逼的 entity_ids |
| slug | string | – | Alias of entity |
No output schema declared.
No examples provided.
intel_global_race ~156
[v1.6.0] L-179 原子：一个品类的全球竞争。必传品类 slug。返回国内 S 码、国外 S 码、差距、对位日期。日期以对位日为准，不是滚动 30 天。非壁垒不给来源 URL；壁垒月卡给来源。只返回 JSON。Atomic global race for one category slug. Domestic S, foreign S, gap, as-of. Not a rolling 30-day feed. Non-pro: no source URLs. Pro: sources. JSON only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Alias of slug |
| slug | string | – | Category slug, e.g. cmp_material |
No output schema declared.
No examples provided.
intel_heal ~133
[v1.6.0] 和本站上次快照比，缺口类型这次没了、还在、或新出现（healed / persistent / new）。会写下这次快照。Compare gap types with this site's last snapshot: gone, still here, or new. Writes this snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | 实体名，如 OpenAI、华为、台积电 |
| entity_id | string | – | 如 ent_openai；与 entity 二选一或并用 |
| window | number | – | 近窗天数 7–90 |
No output schema declared.
No examples provided.
intel_signal ~136
[v1.6.0] 规则缺口（≈list_signals）：落地、商业化、技术，另有链主倒逼无点名承接、海外有卖国内供给空。Rule gaps: landing, commercialization, tech, plus chain-master with no named receiver, and overseas sales with empty China supply.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | 实体名，如 OpenAI、华为、台积电 |
| entity_id | string | – | 如 ent_openai；与 entity 二选一或并用 |
| window | number | – | 近窗天数 7–90 |
No output schema declared.
No examples provided.
intel_tech_daily ~83
[v1.6.0] 技术日报词矩阵，与 /tech-daily 同一批行。公开/免费只亮前 2 条，壁垒全表。Tech-word heat matrix. Public/free: top 2; pro: full.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Snapshot date YYYY-MM-DD. Omit for today. |
No output schema declared.
No examples provided.
intel_tech_dir ~162
[v1.6.0] L-179 原子：一个技术方向。传 dir_id 或方向名。返回阶段、所属品类、线索。新闻线索 90 天，论文 24 个月。非壁垒最多 2 条且不给来源 URL；壁垒月卡给全量线索和 URL。只返回 JSON。Atomic tech direction by dir_id or name. News 90 days, papers 24 months. Non-pro: max 2 clues, no source URL. Pro: full clues with URLs. JSON only.
| Name | Type | Req | Description |
|---|---|---|---|
| dir_id | string | – | Direction id, e.g. robot_world_model |
| name | string | – | 方向中文名，如 机器人世界模型 |
No output schema declared.
No examples provided.
intel_tech_launch ~148
[v1.6.0] L-179 原子：一个品类的技术启动。必传品类 slug。返回作价入股、出资、合资等转化动作，含日期。近窗 48 个月。非壁垒最多 2 条且不给来源 URL；壁垒月卡给该品类全量动作和来源。只返回 JSON。Atomic tech launch for one category slug. Window 48 months. Non-pro: max 2, no source URL. Pro: full actions with sources. JSON only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Alias of slug |
| slug | string | – | Category slug |
No output schema declared.
No examples provided.
How do I install the io.github.erxianzhuangzu/lian-chain-intelligence MCP server?
io.github.erxianzhuangzu/lian-chain-intelligence is a hosted endpoint at https://lian.yisuncloud.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 · lian.yisuncloud.com
claude mcp add --transport http erxianzhuangzu-lian-chain-intelligence 'https://lian.yisuncloud.com/mcp'
What is the io.github.erxianzhuangzu/lian-chain-intelligence MCP server?
io.github.erxianzhuangzu/lian-chain-intelligence is an MCP server listed in the public MCP registry as io.github.erxianzhuangzu/lian-chain-intelligence. Query tech-industry-market chain transmission and entity status. This page covers its hosted endpoint (https://lian.yisuncloud.com/mcp).
Is the io.github.erxianzhuangzu/lian-chain-intelligence MCP server safe to use?
io.github.erxianzhuangzu/lian-chain-intelligence scores 83 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 io.github.erxianzhuangzu/lian-chain-intelligence MCP server expose?
io.github.erxianzhuangzu/lian-chain-intelligence exposes 16 tools: intel_availability, intel_chain, intel_signal, intel_heal, intel_brief, and 11 more. Their descriptions and schemas cost roughly 1,757 tokens of context every time the server is loaded.
Does the io.github.erxianzhuangzu/lian-chain-intelligence MCP server require authentication?
Yes. io.github.erxianzhuangzu/lian-chain-intelligence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.erxianzhuangzu/lian-chain-intelligence MCP server still maintained?
io.github.erxianzhuangzu/lian-chain-intelligence 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.