lian-chain-intelligence

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

Should I use this

Quality & Safety

A
Description quality
81%
Schema completeness
90%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (3)

  • LOWTool 'intel_brief' description lacks action verbin intel_brief
  • LOWTool 'intel_tech_daily' description lacks action verbin intel_tech_daily
  • LOWTool 'intel_category' description lacks action verbin intel_category

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,123Tokens (tool definitions)
~598 BTypical response size
Moderate attention impact (0.88% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://lian.yisuncloud.com/mcpstreamable-http

What it can do

Tool inventory

Tools (8)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪intel_availability(entity, entity_id)

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

Input Schema

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名,如 OpenAI、华为、台积电"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai;与 entity 二选一或并用"
    }
  }
}
⚪intel_chain(entity, entity_id)

[v1.3.0] 全链:timeline、delta_days、vs_prior(≈get_chain)。Full chain: timeline, delta_days, vs_prior.

Input Schema

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名,如 OpenAI、华为、台积电"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai;与 entity 二选一或并用"
    }
  }
}
⚪intel_signal(entity, entity_id, window)

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

Input Schema

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名,如 OpenAI、华为、台积电"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai;与 entity 二选一或并用"
    },
    "window": {
      "type": "number",
      "description": "近窗天数 7–90"
    }
  }
}
⚪intel_heal(entity, entity_id, window)

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

Input Schema

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名,如 OpenAI、华为、台积电"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai;与 entity 二选一或并用"
    },
    "window": {
      "type": "number",
      "description": "近窗天数 7–90"
    }
  }
}
⚪intel_brief(entity, entity_id, window, heal)

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

Input Schema

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名,如 OpenAI、华为、台积电"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai;与 entity 二选一或并用"
    },
    "window": {
      "type": "number",
      "description": "近窗天数 7–90"
    },
    "heal": {
      "type": "string",
      "description": "传 0 可跳过愈合快照写入"
    }
  }
}
⚪intel_tech_daily(date)

[v1.3.0] 技术日报词矩阵,与 /tech-daily 同一批行。无 Key 只给公开前 8 条。Tech-word heat matrix, same rows as /tech-daily. No key: public top 8 only.

Input Schema

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "Snapshot date YYYY-MM-DD. Omit for today."
    }
  }
}
⚪intel_category(slug, category)

[v1.3.0] 单个品类的机会与供给。传 slug,与 /entity/{slug}.json 同一裁剪,不是实体列表。One category opportunity. Pass a slug. Same crop as /entity/{slug}.json. Not the entity index.

Input Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Category slug, e.g. optical_module"
    },
    "category": {
      "type": "string",
      "description": "Alias of slug"
    }
  }
}
⚪intel_chain_master(category, entity, entity_id)

[v1.3.0] 已发布的链主倒逼。承接方不是定点供应商。公开档不给来源 URL。Published chain-master push. Receivers are not designated suppliers. Public tier hides source URLs.

Input Schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "Category slug, e.g. robot_joint"
    },
    "entity": {
      "type": "string",
      "description": "Chain-master name or slug, e.g. 特斯拉"
    },
    "entity_id": {
      "type": "string",
      "description": "e.g. ent_tesla"
    }
  }
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded8 tools