lian-chain-intelligence MCP server
io.github.erxianzhuangzu/lian-chain-intelligenceerxianzhuangzustreamable-httpv1.2.0Scanned
Query tech-industry-market chain transmission and entity status.
16 tools: 16 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
16 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the lian-chain-intelligence MCP server can do
The lian-chain-intelligence MCP server is published by the GitHub account erxianzhuangzu. It has 16 tools. It can create or change data (16 tools: intel_availability, intel_chain, intel_signal, intel_heal and 12 more), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Changes things 16Claude Code: ask
intel_availability[v1.6.0] 先查:available_now、coverage、requires_trigger。建议再调 chain/signal/brief。Check coverage status first: available_now, coverage, requires_trigger.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 先查:available_now、coverage、requires_trigger。建议再调 chain/signal/brief。Check coverage status first: available_now, coverage, requires_trigger. Then chain/signal/brief.
intel_brief[v1.6.0] 规则模板拼的缺口组合:落地、商业化、技术,以及链主、跨境,哪几条在。不是大模型。Template of which gap combination is present.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 规则模板拼的缺口组合:落地、商业化、技术,以及链主、跨境,哪几条在。不是大模型。Template of which gap combination is present. Not an LLM.
intel_category[v1.6.0] 品类全包(肥)。优先用原子工具降 token:intel_category_opportunity / _supply / _demand_pull / _migration。Full category pack.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 品类全包(肥)。优先用原子工具降 token:intel_category_opportunity / _supply / _demand_pull / _migration。Full category pack. Prefer atomic siblings to cut tokens.
intel_category_demand_pull[v1.6.0] L-153a 原子:只出需求倒逼段(signals/chains),公开无 chains。Atomic: demand_pull slice only.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] L-153a 原子:只出需求倒逼段(signals/chains),公开无 chains。Atomic: demand_pull slice only.
intel_category_migration[v1.6.0] L-153a 原子:技术迁移层。非壁垒仅标题示意/锁定;全量需壁垒。Atomic: tech_migration.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] L-153a 原子:技术迁移层。非壁垒仅标题示意/锁定;全量需壁垒。Atomic: tech_migration. Non-pro: teaser/locked only.
intel_category_opportunity[v1.6.0] L-153a 原子:只出品类机会面(海外/价差/切入点等),已按档裁剪。Atomic: opportunity slice only.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] L-153a 原子:只出品类机会面(海外/价差/切入点等),已按档裁剪。Atomic: opportunity slice only.
intel_category_supply[v1.6.0] L-153a 原子:只出品类供给(整机/零部件示意),已按档裁剪。Atomic: supply slice only.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] L-153a 原子:只出品类供给(整机/零部件示意),已按档裁剪。Atomic: supply slice only.
intel_chain[v1.6.0] 全链:timeline、delta_days、vs_prior(≈get_chain)。需 Key。Full chain: timeline, delta_days, vs_prior.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 全链:timeline、delta_days、vs_prior(≈get_chain)。需 Key。Full chain: timeline, delta_days, vs_prior. Requires key.
intel_chain_master[v1.6.0] 已发布的链主倒逼。承接方不是定点供应商。公开/免费档不给来源 URL。Published chain-master push.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 已发布的链主倒逼。承接方不是定点供应商。公开/免费档不给来源 URL。Published chain-master push. Public/free tiers hide source URLs.
intel_demand[v1.6.0] 需求倒逼(品类匿名 signals/chains)。list=1 列实体;或传 entity/slug。公开前 3 条 signal、无 chains。Demand-pull.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 需求倒逼(品类匿名 signals/chains)。list=1 列实体;或传 entity/slug。公开前 3 条 signal、无 chains。Demand-pull. list=1 or entity. Public: 3 signals, no chains.
intel_global_race[v1.6.0] L-179 原子:一个品类的全球竞争。必传品类 slug。返回国内 S 码、国外 S 码、差距、对位日期。日期以对位日为准,不是滚动 30 天。非壁垒不给来源 URL;壁垒月卡给来源。只返回 JSON。Atomic global race for one category slug.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [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.
intel_heal[v1.6.0] 和本站上次快照比,缺口类型这次没了、还在、或新出现(healed / persistent / new)。会写下这次快照。Compare gap types with this site's last snapshot: gone, still here, or new.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 和本站上次快照比,缺口类型这次没了、还在、或新出现(healed / persistent / new)。会写下这次快照。Compare gap types with this site's last snapshot: gone, still here, or new. Writes this snapshot.
intel_signal[v1.6.0] 规则缺口(≈list_signals):落地、商业化、技术,另有链主倒逼无点名承接、海外有卖国内供给空。Rule gaps: landing, commercialization, tech, plus chain-master with no named receiver, and overseas sales with empty Ch…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 规则缺口(≈list_signals):落地、商业化、技术,另有链主倒逼无点名承接、海外有卖国内供给空。Rule gaps: landing, commercialization, tech, plus chain-master with no named receiver, and overseas sales with empty China supply.
intel_tech_daily[v1.6.0] 技术日报词矩阵,与 /tech-daily 同一批行。公开/免费只亮前 2 条,壁垒全表。Tech-word heat matrix.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [v1.6.0] 技术日报词矩阵,与 /tech-daily 同一批行。公开/免费只亮前 2 条,壁垒全表。Tech-word heat matrix. Public/free: top 2; pro: full.
intel_tech_dir[v1.6.0] L-179 原子:一个技术方向。传 dir_id 或方向名。返回阶段、所属品类、线索。新闻线索 90 天,论文 24 个月。非壁垒最多 2 条且不给来源 URL;壁垒月卡给全量线索和 URL。只返回 JSON。Atomic tech direction by dir_id or name.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [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.
intel_tech_launch[v1.6.0] L-179 原子:一个品类的技术启动。必传品类 slug。返回作价入股、出资、合资等转化动作,含日期。近窗 48 个月。非壁垒最多 2 条且不给来源 URL;壁垒月卡给该品类全量动作和来源。只返回 JSON。Atomic tech launch for one category slug.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it [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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:04 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 16
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 16 tools that change things (16 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://lian.yisuncloud.com/mcp: tools/list returned 16 tools to an anonymous client, including intel_availability (write), intel_chain (write), intel_signal (write), intel_heal (write), intel_brief (write) and 11 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 15 to 16
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 15 changed.+1 added~15 changedView diff
- Added:intel_tech_dirChanges things
- Changed:intel_availabilityChanges thingsdescription
- Changed:intel_briefChanges thingsdescription
- Changed:intel_categoryChanges thingsdescription
- Changed:intel_category_demand_pullChanges thingsdescription
- Changed:intel_category_migrationChanges thingsdescription
- Changed:intel_category_opportunityChanges thingsdescription
- Changed:intel_category_supplyChanges thingsdescription
- Changed:intel_chainChanges thingsdescription
- Changed:intel_chain_masterChanges thingsdescription
- Changed:intel_demandChanges thingsdescription
- Changed:intel_global_raceChanges thingsdescriptioninputSchema
- Changed:intel_healChanges thingsdescription
- Changed:intel_signalChanges thingsdescription
- Changed:intel_tech_dailyChanges thingsdescription
- Changed:intel_tech_launchChanges thingsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 15 -> 16.View diff
- Tools that change things, listed without credentials: 15 to 16
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http lian-chain-intelligence https://lian.yisuncloud.com/mcpclaude mcp add --transport http lian-chain-intelligence https://lian.yisuncloud.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__lian-chain-intelligence__intel_availability",
"mcp__lian-chain-intelligence__intel_chain",
"mcp__lian-chain-intelligence__intel_signal",
"mcp__lian-chain-intelligence__intel_heal",
"mcp__lian-chain-intelligence__intel_brief",
"mcp__lian-chain-intelligence__intel_tech_daily",
"mcp__lian-chain-intelligence__intel_tech_dir",
"mcp__lian-chain-intelligence__intel_global_race",
"mcp__lian-chain-intelligence__intel_tech_launch",
"mcp__lian-chain-intelligence__intel_demand",
"mcp__lian-chain-intelligence__intel_category",
"mcp__lian-chain-intelligence__intel_category_opportunity",
"mcp__lian-chain-intelligence__intel_category_supply",
"mcp__lian-chain-intelligence__intel_category_demand_pull",
"mcp__lian-chain-intelligence__intel_category_migration",
"mcp__lian-chain-intelligence__intel_chain_master"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lian-chain-intelligence. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.erxianzhuangzu/lian-chain-intelligence/verify?hash=59951025a5c5699377357c8d614cd9ba3ce989b096289b02647622fd9c339371" | jq -e '.changed == false'Pinned hash 59951025a5c5, from Nov 19, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.erxianzhuangzu/lian-chain-intelligence/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.erxianzhuangzu/lian-chain-intelligence)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:33 UTC.
lian-chain-intelligence MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the lian-chain-intelligence MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 16 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the lian-chain-intelligence MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the lian-chain-intelligence MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the lian-chain-intelligence MCP server have?
- 16 tools: 16 write. intel_availability, intel_chain, intel_signal, intel_heal, intel_brief, intel_tech_daily, intel_tech_dir, intel_global_race and 8 more.
Does the lian-chain-intelligence MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the lian-chain-intelligence MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the lian-chain-intelligence MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.