# io.github.erxianzhuangzu/lian-chain-intelligence (remote · lian.yisuncloud.com)

Query tech-industry-market chain transmission and entity status.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `lian.yisuncloud.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/erxianzhuangzu-lian-chain-intelligence/lian.md), [page](https://verifymcp.io/servers/erxianzhuangzu-lian-chain-intelligence/lian)

## Channel facts

- Endpoint: `https://lian.yisuncloud.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.2.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**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 59/100
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http erxianzhuangzu-lian-chain-intelligence 'https://lian.yisuncloud.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "erxianzhuangzu-lian-chain-intelligence": {
      "url": "https://lian.yisuncloud.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "erxianzhuangzu-lian-chain-intelligence": {
      "type": "http",
      "url": "https://lian.yisuncloud.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.erxianzhuangzu-lian-chain-intelligence]
url = "https://lian.yisuncloud.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "erxianzhuangzu-lian-chain-intelligence": {
      "type": "remote",
      "url": "https://lian.yisuncloud.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add erxianzhuangzu-lian-chain-intelligence --url 'https://lian.yisuncloud.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  erxianzhuangzu-lian-chain-intelligence:
    url: "https://lian.yisuncloud.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "erxianzhuangzu-lian-chain-intelligence": {
      "Transport": "http",
      "Url": "https://lian.yisuncloud.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add erxianzhuangzu-lian-chain-intelligence -t streamable-http -u 'https://lian.yisuncloud.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "erxianzhuangzu-lian-chain-intelligence": {
      "type": "http",
      "url": "https://lian.yisuncloud.com/mcp"
    }
  }
}
```

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-04 (score 83, +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.

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

### 2026-10-31 (score 81, +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.

### 2026-10-29 (score 80, +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.

### 2026-10-28 (score 79, 0)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.5.1 → 1.6.0
- [functional] New tool “intel_tech_dir”
- [cosmetic] “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”

### 2026-10-26 (score 79, +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.

### 2026-10-24 (score 78, +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.

### 2026-10-22 (score 77, +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.

## MCP tools (16)

### `intel_availability` (~99 tokens)

[v1.6.0] 先查：available_now、coverage、requires_trigger。建议再调 chain/signal/brief。Check coverage status first: available_now, coverage, requires_trigger. Then chain/signal/brief.

Input parameters:

- `entity` (string): 实体名，如 OpenAI、华为、台积电
- `entity_id` (string): 如 ent_openai；与 entity 二选一或并用

### `intel_chain` (~89 tokens)

[v1.6.0] 全链：timeline、delta_days、vs_prior（≈get_chain）。需 Key。Full chain: timeline, delta_days, vs_prior. Requires key.

Input parameters:

- `entity` (string): 实体名，如 OpenAI、华为、台积电
- `entity_id` (string): 如 ent_openai；与 entity 二选一或并用

### `intel_signal` (~136 tokens)

[v1.6.0] 规则缺口（≈list_signals）：落地、商业化、技术，另有链主倒逼无点名承接、海外有卖国内供给空。Rule gaps: landing, commercialization, tech, plus chain-master with no named receiver, and overseas sales with empty China supply.

Input parameters:

- `entity` (string): 实体名，如 OpenAI、华为、台积电
- `entity_id` (string): 如 ent_openai；与 entity 二选一或并用
- `window` (number): 近窗天数 7–90

### `intel_heal` (~133 tokens)

[v1.6.0] 和本站上次快照比，缺口类型这次没了、还在、或新出现（healed / persistent / new）。会写下这次快照。Compare gap types with this site's last snapshot: gone, still here, or new. Writes this snapshot.

Input parameters:

- `entity` (string): 实体名，如 OpenAI、华为、台积电
- `entity_id` (string): 如 ent_openai；与 entity 二选一或并用
- `window` (number): 近窗天数 7–90

### `intel_brief` (~140 tokens)

[v1.6.0] 规则模板拼的缺口组合：落地、商业化、技术，以及链主、跨境，哪几条在。不是大模型。Template of which gap combination is present. Not an LLM.

Input parameters:

- `entity` (string): 实体名，如 OpenAI、华为、台积电
- `entity_id` (string): 如 ent_openai；与 entity 二选一或并用
- `heal` (string): 传 0 可跳过愈合快照写入
- `window` (number): 近窗天数 7–90

### `intel_tech_daily` (~83 tokens)

[v1.6.0] 技术日报词矩阵，与 /tech-daily 同一批行。公开/免费只亮前 2 条，壁垒全表。Tech-word heat matrix. Public/free: top 2; pro: full.

Input parameters:

- `date` (string): Snapshot date YYYY-MM-DD. Omit for today.

### `intel_tech_dir` (~162 tokens)

[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.

Input parameters:

- `dir_id` (string): Direction id, e.g. robot_world_model
- `name` (string): 方向中文名，如 机器人世界模型

### `intel_global_race` (~156 tokens)

[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.

Input parameters:

- `category` (string): Alias of slug
- `slug` (string): Category slug, e.g. cmp_material

### `intel_tech_launch` (~148 tokens)

[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.

Input parameters:

- `category` (string): Alias of slug
- `slug` (string): Category slug

### `intel_demand` (~124 tokens)

[v1.6.0] 需求倒逼（品类匿名 signals/chains）。list=1 列实体；或传 entity/slug。公开前 3 条 signal、无 chains。Demand-pull. list=1 or entity. Public: 3 signals, no chains.

Input parameters:

- `entity` (string): 品类 slug/id，如 portable_power
- `entity_id` (string): Alias of entity
- `list` (boolean): true=只列有需求倒逼的 entity_ids
- `slug` (string): Alias of entity

### `intel_category` (~85 tokens)

[v1.6.0] 品类全包（肥）。优先用原子工具降 token：intel_category_opportunity / _supply / _demand_pull / _migration。Full category pack. Prefer atomic siblings to cut tokens.

Input parameters:

- `category` (string): Alias of slug
- `slug` (string): Category slug, e.g. optical_module

### `intel_category_opportunity` (~79 tokens)

[v1.6.0] L-153a 原子：只出品类机会面（海外/价差/切入点等），已按档裁剪。Atomic: opportunity slice only.

Input parameters:

- `category` (string): Alias of slug
- `slug` (string): Category slug, e.g. optical_module

### `intel_category_supply` (~71 tokens)

[v1.6.0] L-153a 原子：只出品类供给（整机/零部件示意），已按档裁剪。Atomic: supply slice only.

Input parameters:

- `category` (string): Alias of slug
- `slug` (string): Category slug

### `intel_category_demand_pull` (~67 tokens)

[v1.6.0] L-153a 原子：只出需求倒逼段（signals/chains），公开无 chains。Atomic: demand_pull slice only.

Input parameters:

- `category` (string): Alias of slug
- `slug` (string): Category slug

### `intel_category_migration` (~82 tokens)

[v1.6.0] L-153a 原子：技术迁移层。非壁垒仅标题示意/锁定；全量需壁垒。Atomic: tech_migration. Non-pro: teaser/locked only.

Input parameters:

- `category` (string): Alias of slug
- `slug` (string): Category slug

### `intel_chain_master` (~103 tokens)

[v1.6.0] 已发布的链主倒逼。承接方不是定点供应商。公开/免费档不给来源 URL。Published chain-master push. Public/free tiers hide source URLs.

Input parameters:

- `category` (string): Category slug, e.g. robot_joint
- `entity` (string): Chain-master name or slug, e.g. 特斯拉
- `entity_id` (string): e.g. ent_tesla

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/erxianzhuangzu-lian-chain-intelligence/lian#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 61

## Common questions

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

### What did VerifyMCP test on the io.github.erxianzhuangzu/lian-chain-intelligence MCP server?

VerifyMCP ran 13 checks on io.github.erxianzhuangzu/lian-chain-intelligence, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://lian.yisuncloud.com/mcp
- Repository: https://github.com/erxianzhuangzu/lian-chain-intelligence
- Changelog RSS feed: https://verifymcp.io/servers/erxianzhuangzu-lian-chain-intelligence/lian.xml
- Changelog JSON feed: https://verifymcp.io/servers/erxianzhuangzu-lian-chain-intelligence/lian/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/erxianzhuangzu-lian-chain-intelligence/lian.json
- HTML version of this page: https://verifymcp.io/servers/erxianzhuangzu-lian-chain-intelligence/lian