cti-expert MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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)

Démo en direct

Aperçu en pratique

cti-expert-skill.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : cti-expert

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

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

Quand l'utiliser : You have an IOC from an alert and need context before escalating.

Prérequis

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

Déroulement

Submit the indicator

Enrich 185.234.218.95 using public OSINT — WHOIS, passive DNS (free sources), reputation feeds.✓ Copié

→ 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.✓ Copié

→ TTP list with ATT&CK IDs
Write up

Produce a tactical report: what it is, confidence level, recommended actions.✓ Copié

→ Short, decision-oriented write-up

Résultat : A defensible enrichment you can attach to a ticket in minutes.

Pièges

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

Combiner avec : filesystem

Draft a campaign write-up from a handful of artifacts

👤 CTI analysts producing internal reports ⏱ ~45 min advanced

Quand l'utiliser : You've been asked to turn a pile of IOCs, TTPs, and notes into a readable brief.

Déroulement

Collate the artifacts

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

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

Map observed behaviors to ATT&CK; note coverage gaps.✓ Copié

→ Coverage matrix
Write the brief

Produce an executive section, a tactical section, and an IOC appendix.✓ Copié

→ 3-part report

Résultat : A consistent, audience-tiered report ready for review.

Pièges

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

Quand l'utiliser : Multiple actors could explain the evidence; you want structure before picking one.

Déroulement

List hypotheses + evidence

Hypotheses: H1, H2, H3. Evidence: E1–E10. Set up the ACH matrix.✓ Copié

→ Matrix with consistency marks per cell
Identify diagnostic evidence

Which evidence items have the highest diagnostic value?✓ Copié

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

Pick the least-inconsistent hypothesis and list what would flip it.✓ Copié

→ Selection + counter-evidence triggers

Résultat : A transparent attribution decision with documented reasoning.

Pièges

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

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
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

Coût et limites

Coût d'exécution

Quota d'API: depends on the OSINT sources used; all default sources are free-tier
Tokens par appel: 2–10k tokens per indicator workflow
Monétaire: free
Astuce: Start with passive sources only; add paid feeds only if coverage gaps justify it

Sécurité

Permissions, secrets, portée

Stockage des identifiants : none by default; any paid feed API key lives in env vars

Sortie de données : 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

Dépannage

Erreurs courantes et correctifs

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

Alternatives

cti-expert vs autres

Alternative	Quand l'utiliser	Compromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills