Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Threadlinqs threat-intelligence MCP — 73 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
THREADLINQS_API_KEY, THREADLINQS_API_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"intelthreadlinqs": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "your-value",
"THREADLINQS_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add intelthreadlinqs --env THREADLINQS_API_KEY=your-value --env THREADLINQS_API_URL=your-value -- npx -y intelthreadlinqs-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"intelthreadlinqs": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "your-value",
"THREADLINQS_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"intelthreadlinqs": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp"
],
"env": {
"THREADLINQS_API_KEY": "your-value",
"THREADLINQS_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
THREADLINQS_API_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain threadlinqs.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: THREADLINQS_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (8.1.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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