cti-expert MCP — 使用场景, 安装 & 实时演示

为什么要用

核心特性

67+ command shortcuts for common CTI tasks
35 analytic techniques (ACH, diamond model, SATs)
MITRE ATT&CK mapping helpers
Public-OSINT only — no API keys, no paid services required
Structured reporting templates (executive, tactical, technical)

实时演示

实际使用效果

cti-expert-skill.replay ▶ 就绪

0/0

安装

选择你的客户端

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "cti-expert-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/7onez/cti-expert",
        "~/.claude/skills/cti-expert"
      ],
      "_inferred": true
    }
  }
}

打开 Claude Desktop → Settings → Developer → Edit Config。保存后重启应用。

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "cti-expert-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/7onez/cti-expert",
        "~/.claude/skills/cti-expert"
      ],
      "_inferred": true
    }
  }
}

Cursor 使用与 Claude Desktop 相同的 mcpServers 格式。项目级配置优先于全局。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "cti-expert-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/7onez/cti-expert",
        "~/.claude/skills/cti-expert"
      ],
      "_inferred": true
    }
  }
}

点击 Cline 侧栏中的 MCP Servers 图标，然后选 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "cti-expert-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/7onez/cti-expert",
        "~/.claude/skills/cti-expert"
      ],
      "_inferred": true
    }
  }
}

格式与 Claude Desktop 相同。重启 Windsurf 生效。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "cti-expert-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/7onez/cti-expert",
        "~/.claude/skills/cti-expert"
      ]
    }
  ]
}

Continue 使用服务器对象数组，而非映射。

~/.config/zed/settings.json

{
  "context_servers": {
    "cti-expert-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/7onez/cti-expert",
          "~/.claude/skills/cti-expert"
        ]
      }
    }
  }
}

加入 context_servers。Zed 保存后热重载。

claude mcp add cti-expert-skill -- git clone https://github.com/7onez/cti-expert ~/.claude/skills/cti-expert

一行命令搞定。用 claude mcp list 验证，claude mcp remove 卸载。

使用场景

实战用法： cti-expert

How to enrich a suspicious indicator (IP, domain, hash) with public OSINT

👤 SOC analysts, incident responders, blue-team engineers ⏱ ~15 min intermediate

何时使用： You have an IOC from an alert and need context before escalating.

前置条件

Skill cloned — git clone https://github.com/7onez/cti-expert ~/.claude/skills/cti-expert

步骤

Submit the indicator

Enrich 185.234.218.95 using public OSINT — WHOIS, passive DNS (free sources), reputation feeds.✓ 已复制

→ Structured context: ASN, geo, historical resolutions, known bad
Map to MITRE ATT&CK if applicable

If this matches a known campaign, map to ATT&CK tactics/techniques.✓ 已复制

→ TTP list with ATT&CK IDs
Write up

Produce a tactical report: what it is, confidence level, recommended actions.✓ 已复制

→ Short, decision-oriented write-up

结果： A defensible enrichment you can attach to a ticket in minutes.

注意事项

Treating reputation scores as ground truth — Record the source + date; note confidence explicitly
OSINT queries accidentally tip off the target — Only use passive sources; no active scanning

搭配使用： filesystem

Draft a campaign write-up from a handful of artifacts

👤 CTI analysts producing internal reports ⏱ ~45 min advanced

何时使用： You've been asked to turn a pile of IOCs, TTPs, and notes into a readable brief.

步骤

Collate the artifacts

Here are the IOCs and notes. Cluster them by diamond-model facet (adversary, capability, infra, victim).✓ 已复制

→ Diamond-model-shaped clustering
Map to ATT&CK

Map observed behaviors to ATT&CK; note coverage gaps.✓ 已复制

→ Coverage matrix
Write the brief

Produce an executive section, a tactical section, and an IOC appendix.✓ 已复制

→ 3-part report

结果： A consistent, audience-tiered report ready for review.

注意事项

Inflating confidence language ('almost certainly') — Force IC-style qualifiers (high/moderate/low) with reasoning

Run an ACH (Analysis of Competing Hypotheses) walk-through

👤 Analysts wrestling with ambiguous attribution ⏱ ~30 min advanced

何时使用： Multiple actors could explain the evidence; you want structure before picking one.

步骤

List hypotheses + evidence

Hypotheses: H1, H2, H3. Evidence: E1–E10. Set up the ACH matrix.✓ 已复制

→ Matrix with consistency marks per cell
Identify diagnostic evidence

Which evidence items have the highest diagnostic value?✓ 已复制

→ Evidence ranked by ability to discriminate
Report the least-inconsistent hypothesis

Pick the least-inconsistent hypothesis and list what would flip it.✓ 已复制

→ Selection + counter-evidence triggers

结果： A transparent attribution decision with documented reasoning.

注意事项

Anchoring on the first hypothesis — Force the matrix first, conclusion last

组合

与其他 MCP 搭配，撬动十倍杠杆

cti-expert-skill + filesystem

Process a directory of raw alerts into structured findings

Enrich every IOC under alerts/2025-04-01/ and produce a consolidated daily tactical report.✓ 已复制

工具

此 MCP 暴露的能力

工具	输入参数	何时调用	成本
indicator-enrichment	IOC (IP/domain/hash/URL)	Triage of any incoming indicator	free OSINT queries
attck-mapping	observed behaviors	When writing up campaigns or detections	0
structured-analytic-techniques	hypotheses + evidence	Ambiguous analysis problems	0
report-templates	findings	Final reporting step	0

成本与限制

运行它的成本

API 配额: depends on the OSINT sources used; all default sources are free-tier
每次调用 Token 数: 2–10k tokens per indicator workflow
费用: free
提示: Start with passive sources only; add paid feeds only if coverage gaps justify it

安全

权限、密钥、影响范围

凭据存储： none by default; any paid feed API key lives in env vars

数据出站： only the OSINT endpoints you allow-list

Strictly defensive use — do not use enrichment output to target individuals or organizations
OSINT queries may be logged by target infrastructure; prefer passive sources
Respect legal frameworks (GDPR, data protection) when handling IOCs tied to persons

故障排查

常见错误与修复

Rate limited by a public source

Throttle or switch to an alternate source — many OSINT endpoints are sensitive

Claude hallucinates an enrichment result

Require citations for every claim; reject unsourced enrichment

ATT&CK mapping is too generic

Provide concrete behaviors (processes, commands, network patterns), not high-level summaries

替代方案

cti-expert 对比其他方案

替代方案	何时用它替代	权衡
claude-cybersecurity-skill	You want broader security skills, not just CTI	Wider but shallower in CTI specifics
claude-security-research-skill	You're researching vulnerabilities rather than triaging indicators	Different job entirely

cti-expert

为什么要用

核心特性

实时演示

实际使用效果

安装

选择你的客户端

使用场景

实战用法： cti-expert

How to enrich a suspicious indicator (IP, domain, hash) with public OSINT

前置条件

步骤

注意事项

Draft a campaign write-up from a handful of artifacts

步骤

注意事项

Run an ACH (Analysis of Competing Hypotheses) walk-through

步骤

注意事项

组合

与其他 MCP 搭配，撬动十倍杠杆

工具

此 MCP 暴露的能力

成本与限制

运行它的成本

安全

权限、密钥、影响范围

故障排查

常见错误与修复

替代方案

cti-expert 对比其他方案

更多

资源