MITRE ATT&CK
Query MITRE ATT&CK tactics, techniques, and related knowledge from your agent while reviewing threats, test plans, or security docs.
Overview
io.github.luongnv89/mitre-mcp is a Ship-phase MCP server that exposes the MITRE ATT&CK framework to agents via the official MCP Python SDK.
What is this MCP server?
- MCP server for MITRE ATT&CK using the official MCP Python SDK
- PyPI package mitre-mcp at version 0.3.1 with stdio transport
- Title published as MITRE ATT&CK in server metadata
- Suited for threat modeling and control mapping inside agent chats
- Open source via Montimage/mitre-mcp on GitHub
- PyPI package mitre-mcp version 0.3.1
- Server title MITRE ATT&CK in published schema
- Stdio transport; repository Montimage/mitre-mcp on GitHub
Community signal: 11 GitHub stars.
What problem does it solve?
Security reviews in agent sessions drift into vague advice because MITRE ATT&CK is too heavy to browse manually while you code.
Who is it for?
Solo builders and small teams shipping web or API products who want ATT&CK-grounded security copy and test ideas inside Claude Code or Cursor.
Skip if: Builders who need automated vulnerability scanning only or who are still in pure Idea research with no security surface yet.
What do I get? / Deliverables
After installing mitre-mcp, your agent can query ATT&CK-aligned knowledge during threat modeling and pre-ship security discussions.
- Agent-queryable MITRE ATT&CK framework data during security tasks
- Threat-informed technique and mitigation references in review or planning chats
Recommended MCP Servers
Journey fit
ATT&CK grounding matters during Ship when you harden the product, write security stories, and align tests with real adversary behavior before launch. Security is the canonical shelf because the server exposes the MITRE ATT&CK framework for threat-informed decisions, not generic coding or deployment.
How it compares
ATT&CK reference MCP server, not a DAST scanner or generic code-review skill.
Common Questions / FAQ
Who is io.github.luongnv89/mitre-mcp for?
It is for developers and indie security-minded builders who want MITRE ATT&CK accessible from MCP agents during ship and review work.
When should I use io.github.luongnv89/mitre-mcp?
Use it during Ship security subphase when writing threat models, aligning tests to techniques, or explaining risks in launch documentation.
How do I add io.github.luongnv89/mitre-mcp to my agent?
Install the PyPI package mitre-mcp, configure stdio MCP in your client, and point to the mitre-mcp entry from the published server schema.