# intelthreadlinqs-mcp

> intelthreadlinqs-mcp, an MCP server by threadlinqs.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Threadlinqs threat-intelligence MCP — 73 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs

- Canonical: https://www.anchorterminal.com/tools/intelthreadlinqs-mcp
- Markdown: https://www.anchorterminal.com/tools/intelthreadlinqs-mcp.md (~450 tokens)
- Slim: https://www.anchorterminal.com/tools/intelthreadlinqs-mcp.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/intelthreadlinqs-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

# intelthreadlinqs-mcp

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by threadlinqs.com (https://threadlinqs.com)
- Listed because: It's published in the registry under threadlinqs.com, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: Threadlinqs threat-intelligence MCP — 73 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs

## Facts

- MCP registry: `com.threadlinqs/intelthreadlinqs-mcp` 8.1.1
- Package: npm `intelthreadlinqs-mcp` (stdio)
- Source: https://github.com/threadlinqs-cmd/intelthreadlinqs-mcp
- npm downloads a week: 91
- GitHub stars: 0
- Registry entry updated: 2026-08-03

- JSON: https://www.anchorterminal.com/api/v1/tools/intelthreadlinqs-mcp.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming