Ermöglicht KI-Agenten den Zugriff auf Threat Intelligence, einschließlich über 1.700 Bedrohungen, 47.000+ IOCs, Detection Rules und MITRE ATT&CK Mapping.
Auch bekannt als threadlinqs-cmd/intelthreadlinqs-mcp
- Stars
- 0
- Tools
- 3
- Downloads, 30 Tage
- —
- Neueste Version
- 8.1.1
- Letzter Commit
- 23. Aug. 2026
- Lizenz
- MIT
Was ist Threadlinqs Intelligence MCP?
Ermöglicht KI-Agenten den Zugriff auf Threat Intelligence, einschließlich über 1.700 Bedrohungen, 47.000+ IOCs, Detection Rules und MITRE ATT&CK Mapping. Er stellt 3 Tools bereit, etwa search_actors, get_actor, get_similar_threats.
Zusammenfassung generiert aus dem README des Projekts
Über Threadlinqs Intelligence MCP server
Security Analysts und Entwickler können KI-Agenten mit tiefgreifender Threat Intelligence ausstatten, indem sie diesen Server mit Clients wie Claude Desktop, Cursor oder Claude Code verbinden. Er bietet Zugriff auf ein riesiges Repository mit über 1.700 Bedrohungen, 47.000 Indicators of Compromise und 16.000 Detection Rules, formatiert für Splunk, Microsoft KQL und Sigma. Der Server funktioniert via stdio und benötigt eine THREADLINQS_API_KEY Umgebungsvariable für den Betrieb.
Der Zugriff auf die 81 verfügbaren Tools ist auf Nutzer mit einem Purple- oder Gold-Abonnement beschränkt. Während der Server startet und Clients erlaubt, den Tool-Katalog mit Keys aus niedrigeren Tiers zu inspizieren, erfolgt der eigentliche Datenabruf serverseitig durch eine Zugriffsbeschränkung. Nutzer können spezialisierte Tools wie get_threat_hunting_bundle für vollständige Dossiers oder get_mitre_gap_analysis nutzen, um Detection Debt zu identifizieren. Das System enthält zudem 25 Analyst-Playbook-Prompts, die Agenten dabei unterstützen, komplexe Workflows wie CVE Triage oder Actor Profiling zu orchestrieren.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Threadlinqs Intelligence MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenThreadlinqs Intelligence MCP in Claude Code installieren
$ claude mcp add --env 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' intelthreadlinqs-mcp -- npx -y intelthreadlinqs-mcpThreadlinqs Intelligence MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"intelthreadlinqs-mcp": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}Threadlinqs Intelligence MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"intelthreadlinqs-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}Threadlinqs Intelligence MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"intelthreadlinqs-mcp","type":"stdio","command":"npx","args":["-y","intelthreadlinqs-mcp"],"env":{"THREADLINQS_API_KEY":"<YOUR_THREADLINQS_API_KEY>"}}'Threadlinqs Intelligence MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"intelthreadlinqs-mcp": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}Threadlinqs Intelligence MCP in Codex installieren
$ codex mcp add intelthreadlinqs-mcp --env 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' -- npx -y intelthreadlinqs-mcpThreadlinqs Intelligence MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.intelthreadlinqs-mcp] command = "npx" args = ["-y", "intelthreadlinqs-mcp"] [mcp_servers.intelthreadlinqs-mcp.env] THREADLINQS_API_KEY = "<YOUR_THREADLINQS_API_KEY>"
Threadlinqs Intelligence MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' intelthreadlinqs-mcp npx -- -y intelthreadlinqs-mcpThreadlinqs Intelligence MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"intelthreadlinqs-mcp": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}Threadlinqs Intelligence MCP tools 3
Erkannt aus dem READMEsearch_actorsget_actorget_similar_threats
| search_actors | — | |
| get_actor | — | |
| get_similar_threats | — |
Konfiguration
THREADLINQS_API_KEYErforderlichSecretThreadlinqs API key (Purple or Gold tier, tl_...) — get one at https://intel.threadlinqs.com/profile
THREADLINQS_API_URLOverride the API base URL (defaults to https://intel.threadlinqs.com)
| Name | Beschreibung | Typ |
|---|---|---|
| THREADLINQS_API_KEY | Threadlinqs API key (Purple or Gold tier, tl_...) — get one at https://intel.threadlinqs.com/profile | ErforderlichSecret |
| THREADLINQS_API_URL | Override the API base URL (defaults to https://intel.threadlinqs.com) |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarthreadlinqs-cmd/intelthreadlinqs-mcp is public and reachablegithub.com/threadlinqs-cmd/intelthreadlinqs-mcp ↗Bestanden
- Paket nennt dieses Repository als Quelleintelthreadlinqs-mcp names threadlinqs-cmd/intelthreadlinqs-mcp as sourcenpmjs.com/package/intelthreadlinqs-mcp ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)No build attestation published for this releaseNicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-08-23github.com/threadlinqs-cmd/intelthreadlinqs-mcp ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from intelthreadlinqs-mcpBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeiten99 resolved dependencies checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNo tool named like delete, drop or execBestanden
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenintelthreadlinqs-mcp
MCP server for Threadlinqs Intelligence — 81 tools and 25 analyst-playbook prompts across threat intelligence, detections, IOCs, threat actors, MITRE attack-chains, C2 infrastructure, and Purple-tier composite intelligence. Drop-in for Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.
What this gives your AI agent
- 1,700+ threats with full metadata, severity, attribution, CVE/CWE, MITRE
- 16,000+ detection rules in Splunk SPL, Microsoft KQL, and Sigma YAML
- 47,000+ IOCs (IPs, domains, hashes, URLs, behavioral)
- 500+ threat actors with TTPs profiles and cross-actor infrastructure links
- 140+ live C2 beacons (Cobalt Strike) with watermark clustering + operator attribution
- Daily intelligence debriefs + 7-engine correlation analytics
- MITRE attack-chain prediction based on 4,271 observed technique transitions
Quick install
# No install needed — npx will fetch it
npx -y intelthreadlinqs-mcp
Claude Code
claude mcp add threadlinqs-intel \
-e THREADLINQS_API_KEY=tl_your_key_here \
-- npx -y intelthreadlinqs-mcp
The -e THREADLINQS_API_KEY is required in practice. The Threadlinqs Intelligence MCP server is a Purple-tier feature — it checks your key's tier at startup and warns if it is missing, invalid, or below Purple. The server still starts and exposes its tool catalog so clients and registries can introspect it, but tool calls are gated server-side: without a Purple or Gold key (tier ≥ 3) they return an Access denied error instead of data. There is no free or anonymous access to gated intelligence.
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"threadlinqs-intel": {
"command": "npx",
"args": ["-y", "intelthreadlinqs-mcp"],
"env": {
"THREADLINQS_API_KEY": "tl_your_key_here"
}
}
}
}
Cursor
.cursor/mcp.json:
{
"mcpServers": {
"threadlinqs-intel": {
"command": "npx",
"args": ["-y", "intelthreadlinqs-mcp"],
"env": {
"THREADLINQS_API_KEY": "tl_your_key_here"
}
}
}
}
VS Code
.vscode/mcp.json:
{
"servers": {
"threadlinqs-intel": {
"type": "stdio",
"command": "npx",
"args": ["-y", "intelthreadlinqs-mcp"],
"env": {
"THREADLINQS_API_KEY": "tl_your_key_here"
}
}
}
}
Getting an API key
Sign up at intel.threadlinqs.com, verify your email, and head to Profile → API Key. Note that signing up alone lands you on Blue (tier 1) — MCP tool calls need tier ≥ 3, so they return an under-tier error until you upgrade. A 7-day Purple free trial is offered at checkout on the pricing page.
Access — Purple tier only
The MCP server is a Purple-tier feature: all 81 tools require a Purple or Gold subscription (tier ≥ 3). The server checks your key's tier at startup and warns when it is missing, invalid, or below Purple — it still starts and lists its tools so clients can introspect the catalog, but the tier is enforced server-side on every call, so gated tools return Access denied rather than data. There is no free or anonymous access to gated intelligence.
| Tier | Price | MCP access |
|---|---|---|
| Purple | $11.99/mo | ✅ All 81 tools |
| Gold | Custom | ✅ All 81 tools (team — contact sales) |
| Lower tiers | — | ❌ No MCP access (the public website + REST API keep their own free Blue tier) |
A 7-day Purple free trial is available at checkout on the pricing page — it is not granted by signup alone. Tool calls enforce the tier server-side and return a structured 403 if your subscription lapses.
v4.3 flagship tools (Purple tier)
The composite tools are the reason most people upgrade to Purple — each one replaces 5–7 single-purpose MCP calls.
get_threat_hunting_bundle ⭐
Input: threat_id (e.g. "TL-2026-0599")
Returns: complete hunt dossier in one shot — threat metadata, full IOC list, SPL/KQL/Sigma detection queries, similar threats, simulation commands, and cross-threat infrastructure pivots. The single most useful tool in the platform.
get_actor_intelligence
Input: actor name (e.g. "Lazarus Group", "APT29")
Returns: comprehensive adversary picture — actor profile, attributed threats, MITRE techniques, IOCs (200 cap), detection rules (100 cap), activity timeline, active C2 infrastructure correlated to the actor, and cross-actor shared entities.
get_ioc_intelligence
Input: ioc_value (IP, domain, hash, URL)
Returns: every threat that touches the IOC + actor attribution + DNS enrichment trail + cross-IOC infrastructure pivots + consensus confidence score across 7 external feeds (Pulsedive, GreyNoise, YARAify, MalwareBazaar, URLScan, VxVault, OpenPhish). The "I found this in a log — tell me everything" workflow.
get_cve_intelligence
Input: cve_id (e.g. "CVE-2024-3400")
Returns: CVE detail + linked threats + EPSS exploitation velocity + KEV status + detection coverage % + available attack simulations + first-weaponization timeline.
get_mitre_gap_analysis
Input: optional tactic filter, limit
Returns: prioritized list of MITRE techniques without detection coverage, sorted by debt score (threat exposure + KEV count + EPSS). Each entry includes example threats and recommended detection types. Answers "what should I write detections for next?"
predict_mitre_transitions
Input: technique_id (e.g. "T1566"), top_n, direction (forward | reverse)
Returns: ranked next-technique predictions with probability and observation count, plus example threats showing the chain. Built from 4,271 observed transitions across the corpus.
generate_c2_blocklist
Input: none.
Returns: firewall-ready blocklist of active C2 IPs with country, ASN, version, watermark, and last-seen metadata. Currently tracking Cobalt Strike beacons. For operator clustering call get_c2, and for unmasked C2 domains get_c2_dns_intel.
Specialized tools
search_actors— Find threat actors by name, alias, nation-state, or motivation.get_actor— Full actor dossier in a single call.get_similar_threats— Precomputed-similarity matches by shared TTPs, IOC overlap, and same-actor attribution.
Agent skill
A portable skill that teaches any MCP client how to route across these tools — which tool to
call first, the hunt query grammar, the response budget, and the data caveats that keep
answers honest. Generated from the live catalog, so its tool reference cannot drift.
- Single file (paste into any assistant): https://intel.threadlinqs.com/mcp/skill.md
- Bundle (
SKILL.md+references/, for Claude Desktop / API skill upload): https://intel.threadlinqs.com/skills/intelthreadlinqs-mcp-skill.zip - Also in this repo under
skill/, and linked from https://intel.threadlinqs.com/mcp.
Prompts — 25 analyst playbooks
Prompts are pre-built workflows that orchestrate the tools for you. Rather than working out which of 81 tools to chain, invoke a playbook and the agent gets an ordered, argument-correct plan. Between them they reach every tool on the server, so an agent that only reads prompts/list still finds the whole surface.
| Playbook | What it does |
|---|---|
orient |
Start here — catalog, corpus shape, categories, TLQL grammar |
triage_cve |
CVE end-to-end: severity, exploitation, exposure, remediation |
profile_actor |
Actor dossier: TTPs, targeting, attribution confidence |
hunt_ioc |
Indicator → linked threats, blast radius, blocking action |
hunt_corpus |
Aggregate questions in TLQL over the hunt index |
research_question |
Open-ended research via semantic corpus search |
map_detections_to_mitre |
Map a threat's SPL/KQL/Sigma to ATT&CK, flag gaps |
review_detection_gaps |
Highest-value detection debt, ranked by exposure |
write_detection |
Draft a deployable rule grounded in corpus logic |
predict_next_move |
Forecast the next (or preceding) ATT&CK techniques |
explain_link |
Why two threats are linked, with the evidence |
map_campaign |
Campaign members, shared infra, pivotal entities |
review_attribution |
Audit whether an attribution is evidence-backed |
pivot_infrastructure |
Pivot across DNS, hosting and adjacent infrastructure |
malware_dossier |
Profile a malware family or offensive tool |
build_c2_blocklist |
Firewall-ready C2 blocklist with operator clustering |
osint_sweep |
Fold community signal in; surface coverage lead time |
sweep_vulnerabilities |
Triage by exploitability, not CVSS alone |
plan_purple_team |
Simulations paired with the detections they should trip |
export_for_tooling |
STIX 2.1, ATT&CK Navigator, SIEM-ready rules |
bulk_enrich |
Batch a list of threat/CVE ids without N round-trips |
assess_exposure |
Covered vs uncovered for a CVE, actor or technique |
daily_brief |
Today's posture, top new threats, daily theme |
period_review |
Review a day or span from the debrief archive |
platform_status |
Corpus health, engine state, enrichment completeness |
Full tool catalog
For the complete list of 81 tools with parameters and example invocations, see the interactive MCP documentation page.
Architecture
-
Transport: stdio (local subprocess)
-
Auth:
THREADLINQS_API_KEYenvironment variable (Bearer token to the worker API) -
Runtime: Node ≥18
-
SDK:
@modelcontextprotocol/sdk@^1.26.0 -
Backend: Cloudflare Workers + D1 (multi-region)
-
Purple gate: the server checks the API key's tier at startup and warns if it is missing, invalid, or below Purple/Gold (tier ≥ 3) — it starts regardless so the tool catalog stays introspectable; the gate itself is enforced server-side on every tool call (structured 403 on lapse or under-tier)
-
Introspection has three tiers (since 8.1.0): authenticated
tools/list→ the public/mcp/catalog.json→ a catalog snapshot bundled in the package. The first two need network; the third does not, sotools/listreturns the real catalog even in a fully network-isolated sandbox. Previously that case returned an empty array — not an error, an empty list, which is indistinguishable from a server with no tools, and is why registry scanners indexed this server with zero tools.Maintainers: regenerate the snapshot with
npm run sync:catalogafter deploying the worker, since the worker owns the tool and prompt registries.npm run test:catalogfails the build when the snapshot and the live catalog disagree, and it runs onprepublishOnly.
Links
License
MIT © Threadlinqs
Threadlinqs Intelligence MCP Fragen
Wie füge ich Threadlinqs Intelligence MCP zu Claude Code hinzu?
Führe claude mcp add --env 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' intelthreadlinqs-mcp -- npx -y intelthreadlinqs-mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Threadlinqs Intelligence MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet Threadlinqs Intelligence MCP?
Er stellt 3 Tools bereit, darunter search_actors, get_actor, get_similar_threats.
Gibt es eine kostenlose Version?
Die Anmeldung bietet zwar Zugriff auf den Blue-Tier, aber für MCP Tool Calls ist ein Purple- oder Gold-Abonnement erforderlich. Ein 7-tägiger kostenloser Testzeitraum für Purple ist beim Checkout auf der Pricing-Seite verfügbar.
Welche Arten von Detection Rules bietet der Server an?
Der Server enthält über 16.000 Detection Rules im Format Splunk SPL, Microsoft KQL und Sigma YAML.