Mitre Attck

io.github.pipeworx-iov0.1.2Updated Oct 1, 2026

MITRE ATT&CK MCP — STIX bundles from github.com/mitre/cti.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringKnowledge & Memory

Overview

AI-generated overview

Lets an assistant look up MITRE ATT&CK adversary tactics, techniques, groups, software, and mitigations from official STIX bundles.

What it does
Serves MITRE ATT&CK data sourced from MITRE's official STIX 2.1 bundles, cached for one hour. Tools include technique(id), tactic(id_or_short_name), group(id), software(id), mitigation(id), search(query, type?), and domains() for the enterprise, mobile, and ics bundles. It can be reached as a remote endpoint or run locally as a stdio server.
When to use it
Useful when an assistant needs to map threat activity to ATT&CK identifiers, explain a technique or group, or search the ATT&CK corpus during security analysis and reporting. Choose it when you want structured ATT&CK lookups rather than general web search.
Requirements
A remote streamable HTTP endpoint at the gateway, or Node.js with npx for the local stdio package. No account, API key, or environment variable is declared for basic calls; network access is needed to fetch the upstream STIX bundles.
Before you install
The remote pack endpoint also exposes shared gateway meta-tools such as ask_pipeworx, discover_tools, search_within, and remember/recall, which add schemas and may route questions beyond this pack. The local stdio package lists only this pack's tools. Data is read-only reference material; verify ATT&CK identifiers against MITRE before relying on them.

Installation

In SourceWeft

  1. Open Mitre Attck in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mitre-attck": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/mitre-attck/mcp"
    }
  }
}

README

@pipeworx/mitre-attck

MITRE ATT&CK MCP — adversary tactics, techniques, and procedures (TTPs). Sources the official STIX 2.1 bundles from MITRE's GitHub. Cached 1h in-pack.

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

  • technique(id) — technique by ATT&CK id (e.g. T1190, T1059.001)
  • tactic(id_or_short_name) — tactic record
  • group(id) — threat group (e.g. G0007 APT28)
  • software(id) — software/malware (e.g. S0002 Mimikatz)
  • mitigation(id) — mitigation
  • search(query, type?) — substring search across the bundle
  • domains() — list loaded STIX bundles (enterprise, mobile, ics)

Data source

https://raw.githubusercontent.com/mitre/cti/master/enterprise-attack/enterprise-attack.json (and mobile + ics).

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "mitre-attck": {      "url": "https://gateway.pipeworx.io/mitre-attck/mcp"    }  }}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/mitre-attck/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

json
{  "mcpServers": {    "pipeworx": {      "url": "https://gateway.pipeworx.io/mcp"    }  }}

Both URLs reach the same gateway and the same 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

bash
curl -X POST https://gateway.pipeworx.io/v1/tools/technique \  -H 'Content-Type: application/json' \  -d '{"id":"T1566"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/technique. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

json
{  "mcpServers": {    "mitre-attck": {      "command": "npx",      "args": ["-y", "@pipeworx/mcp-mitre-attck"]    }  }}

Or run it directly to confirm it starts:

bash
npx -y @pipeworx/mcp-mitre-attck

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Mitre Attck data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Source: README.md at commit cd4330e

Tools

0
Tool metadata has not been indexed yet.

Version history

3
  1. v0.1.2LatestSep 27, 2026
  2. v0.1.1Sep 25, 2026
  3. v0.1.0Sep 16, 2026