原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Intelthreadlinqs MCP

作者:threadlinqs-cmd版本 7.1.3i★ –i在你的电脑上运行
注册名称io.github.threadlinqs-cmd/intelthreadlinqs-mcp

安装

概览

作者提供的说明(英文原文)

Threadlinqs threat-intelligence MCP — 49 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他
  • 你需要填写:THREADLINQS_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: THREADLINQS_API_KEY, THREADLINQS_API_URL

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 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 中打开

或者自己复制设置

粘贴到项目中的 .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"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .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_KEY 机密 必填 env
    Threadlinqs API key (Purple or Gold tier, tl_...) — get one at https://intel.threadlinqs.com/profile
  • THREADLINQS_API_URL env
    Override the API base URL (defaults to https://intel.threadlinqs.com)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 threadlinqs-cmd 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32371 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32371 个服务器的 18% 更新
  • 基础检查结果等于或优于此分类中其他 32371 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Intelthreadlinqs MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:THREADLINQS_API_KEY

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(7.1.3)于4个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Opencu

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

Opencu

作者:Daily-AC

Independent local computer-use engine and MCP server for macOS, Windows, Linux and Android

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

TierPriceMCP access
Purple$11.99/mo✅ All 81 tools
GoldCustom✅ 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.

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.

PlaybookWhat it does
orientStart here — catalog, corpus shape, categories, TLQL grammar
triage_cveCVE end-to-end: severity, exploitation, exposure, remediation
profile_actorActor dossier: TTPs, targeting, attribution confidence
hunt_iocIndicator → linked threats, blast radius, blocking action
hunt_corpusAggregate questions in TLQL over the hunt index
research_questionOpen-ended research via semantic corpus search
map_detections_to_mitreMap a threat's SPL/KQL/Sigma to ATT&CK, flag gaps
review_detection_gapsHighest-value detection debt, ranked by exposure
write_detectionDraft a deployable rule grounded in corpus logic
predict_next_moveForecast the next (or preceding) ATT&CK techniques
explain_linkWhy two threats are linked, with the evidence
map_campaignCampaign members, shared infra, pivotal entities
review_attributionAudit whether an attribution is evidence-backed
pivot_infrastructurePivot across DNS, hosting and adjacent infrastructure
malware_dossierProfile a malware family or offensive tool
build_c2_blocklistFirewall-ready C2 blocklist with operator clustering
osint_sweepFold community signal in; surface coverage lead time
sweep_vulnerabilitiesTriage by exploitability, not CVSS alone
plan_purple_teamSimulations paired with the detections they should trip
export_for_toolingSTIX 2.1, ATT&CK Navigator, SIEM-ready rules
bulk_enrichBatch a list of threat/CVE ids without N round-trips
assess_exposureCovered vs uncovered for a CVE, actor or technique
daily_briefToday's posture, top new threats, daily theme
period_reviewReview a day or span from the debrief archive
platform_statusCorpus 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_KEY environment 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, 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.

Links

License

MIT © Threadlinqs

问 PopNx