1,700개 이상의 위협 정보, 47,000개 이상의 IOC, 탐지 규칙 및 MITRE ATT&CK 매핑을 포함한 위협 인텔리전스를 AI agent에게 제공합니다.
다른 이름 threadlinqs-cmd/intelthreadlinqs-mcp
- 스타
- 0
- Tools
- 3
- 다운로드, 30일
- —
- 최신 버전
- 8.1.1
- 마지막 커밋
- 2026년 8월 23일
- 라이선스
- MIT
Threadlinqs Intelligence MCP란?
1,700개 이상의 위협 정보, 47,000개 이상의 IOC, 탐지 규칙 및 MITRE ATT&CK 매핑을 포함한 위협 인텔리전스를 AI agent에게 제공합니다. 3개 도구를 제공합니다. 예: search_actors, get_actor, get_similar_threats.
프로젝트 README에서 생성된 요약
Threadlinqs Intelligence MCP server 정보
보안 분석가와 개발자는 이 서버를 Claude Desktop, Cursor 또는 Claude Code와 같은 클라이언트에 연결하여 AI agent에 심층적인 위협 인텔리전스 기능을 부여할 수 있습니다. 1,700개 이상의 위협, 47,000개의 침해 지표(IOC), 그리고 Splunk, Microsoft KQL, Sigma 형식으로 제공되는 16,000개의 탐지 규칙이 포함된 방대한 저장소에 접근할 수 있습니다. 서버는 stdio를 통해 작동하며 실행을 위해 THREADLINQS_API_KEY 환경 변수가 필요합니다.
사용 가능한 81개 도구에 대한 접근 권한은 Purple 또는 Gold 구독 티어 사용자에게 제한됩니다. 낮은 티어의 키를 사용하더라도 서버가 시작되고 클라이언트가 도구 카탈로그를 조사할 수는 있지만, 실제 데이터 검색은 서버 측에서 제한됩니다. 사용자는 전체 정보를 확인하기 위한 get_threat_hunting_bundle나 탐지 공백을 식별하기 위한 get_mitre_gap_analysis와 같은 특화된 도구를 활용할 수 있습니다. 또한 시스템에는 CVE 분류 또는 공격자 프로파일링과 같은 복잡한 워크플로우를 agent가 수행할 수 있도록 돕는 25개의 분석 플레이북 프롬프트가 포함되어 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Threadlinqs Intelligence MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Threadlinqs Intelligence MCP 설치
$ claude mcp add --env 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' intelthreadlinqs-mcp -- npx -y intelthreadlinqs-mcpCursor에 Threadlinqs Intelligence MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"intelthreadlinqs-mcp": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}VS Code에 Threadlinqs Intelligence MCP 설치
.vscode/mcp.json
{
"servers": {
"intelthreadlinqs-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}VS Code CLI에 Threadlinqs Intelligence MCP 설치
$ code --add-mcp '{"name":"intelthreadlinqs-mcp","type":"stdio","command":"npx","args":["-y","intelthreadlinqs-mcp"],"env":{"THREADLINQS_API_KEY":"<YOUR_THREADLINQS_API_KEY>"}}'Claude Desktop에 Threadlinqs Intelligence MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"intelthreadlinqs-mcp": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}Codex에 Threadlinqs Intelligence MCP 설치
$ codex mcp add intelthreadlinqs-mcp --env 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' -- npx -y intelthreadlinqs-mcpCodex config.toml에 Threadlinqs Intelligence MCP 설치
~/.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>"
Gemini CLI에 Threadlinqs Intelligence MCP 설치
$ gemini mcp add -s user -e 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' intelthreadlinqs-mcp npx -- -y intelthreadlinqs-mcpGemini settings.json에 Threadlinqs Intelligence MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"intelthreadlinqs-mcp": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "<YOUR_THREADLINQS_API_KEY>"
}
}
}
}Threadlinqs Intelligence MCP 도구 3
README에서 감지됨search_actorsget_actorget_similar_threats
| search_actors | — | |
| get_actor | — | |
| get_similar_threats | — |
구성
THREADLINQS_API_KEY필수비밀Threadlinqs 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)
| 이름 | 설명 | 유형 |
|---|---|---|
| THREADLINQS_API_KEY | Threadlinqs API key (Purple or Gold tier, tl_...) — get one at https://intel.threadlinqs.com/profile | 필수비밀 |
| THREADLINQS_API_URL | Override the API base URL (defaults to https://intel.threadlinqs.com) |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능threadlinqs-cmd/intelthreadlinqs-mcp is public and reachablegithub.com/threadlinqs-cmd/intelthreadlinqs-mcp ↗통과
- 패키지가 이 저장소를 소스로 명시intelthreadlinqs-mcp names threadlinqs-cmd/intelthreadlinqs-mcp as sourcenpmjs.com/package/intelthreadlinqs-mcp ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-08-23github.com/threadlinqs-cmd/intelthreadlinqs-mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from intelthreadlinqs-mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음99 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음3 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기intelthreadlinqs-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 질문
Threadlinqs Intelligence MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'THREADLINQS_API_KEY=<YOUR_THREADLINQS_API_KEY>' intelthreadlinqs-mcp -- npx -y intelthreadlinqs-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Threadlinqs Intelligence MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Threadlinqs Intelligence MCP는 어떤 도구를 제공하나요?
3개 도구를 제공합니다. 예: search_actors, get_actor, get_similar_threats.
무료 티어가 있나요?
가입 시 Blue 티어를 사용할 수 있지만, MCP tool 호출을 위해서는 Purple 또는 Gold 구독이 필요합니다. 요금 페이지의 결제 단계에서 7일간의 Purple 무료 체험을 이용할 수 있습니다.
어떤 종류의 탐지 규칙을 제공하나요?
이 서버는 Splunk SPL, Microsoft KQL, Sigma YAML 형식으로 작성된 16,000개 이상의 탐지 규칙을 포함합니다.