Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Threadlinqs threat-intelligence MCP — 73 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
THREADLINQS_API_KEY, THREADLINQS_API_URL「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"intelthreadlinqs": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "your-value",
"THREADLINQS_API_URL": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add intelthreadlinqs --env THREADLINQS_API_KEY=your-value --env THREADLINQS_API_URL=your-value -- npx -y intelthreadlinqs-mcp動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"intelthreadlinqs": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "your-value",
"THREADLINQS_API_URL": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"intelthreadlinqs": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "your-value",
"THREADLINQS_API_URL": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
THREADLINQS_API_URL envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名はドメイン threadlinqs.com で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:THREADLINQS_API_KEY
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(8.1.1)がレジストリに届いたのは3 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, LickityClick
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
# No install needed — npx will fetch it
npx -y intelthreadlinqs-mcp
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.
~/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/mcp.json:
{
"mcpServers": { "threadlinqs-intel": { "command": "npx", "args": ["-y", "intelthreadlinqs-mcp"], "env": { "THREADLINQS_API_KEY": "tl_your_key_here" } } } }
.vscode/mcp.json:
{
"servers": { "threadlinqs-intel": { "type": "stdio", "command": "npx", "args": ["-y", "intelthreadlinqs-mcp"], "env": { "THREADLINQS_API_KEY": "tl_your_key_here" } } } }
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.
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.
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_intelligenceInput: 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_intelligenceInput: 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_intelligenceInput: 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_analysisInput: 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_transitionsInput: 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_blocklistInput: 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.
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.
SKILL.md + references/, for Claude Desktop / API skill upload): https://intel.threadlinqs.com/skills/intelthreadlinqs-mcp-skill.zipskill/, and linked from https://intel.threadlinqs.com/mcp.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 |
For the complete list of 81 tools with parameters and example invocations, see the interactive MCP documentation page.
THREADLINQS_API_KEY environment variable (Bearer token to the worker API)@modelcontextprotocol/sdk@^1.26.0tools/list → the public /mcp/catalog.json → a catalog snapshot bundled in the package. The first two need network; the third does not, so tools/list returns 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:catalog after deploying the worker, since the worker owns the tool and prompt registries. npm run test:catalog fails the build when the snapshot and the live catalog disagree, and it runs on prepublishOnly.
MIT © Threadlinqs