A CLI, TUI & MCP Server for https://emb3d.mitre.org/
uvx mitre-emb3d --helpor
uvx --from mitre-emb3d med --help
uvx --from mitre-emb3d med --pprint properties Networking --level 3The project can be used both as a tool & library
uv add mitre-emb3d- Hardware
- System Software
- Application Software
- Networking
- List device properties for a given category
- List threats for a given category
- List mitigations for a given threat
- Get detailed information about a threat
- Get detailed information about a mitigation
- A CLI - AI Agent first (returns JSON output) / For humans add
--pprintto see beautiful ouput - A TUI - Heatmap creation, reading & update (See TUI section below for screenshots)
- An MCP Server
- ... more coming
Example -
$ uv run med --pprint threats "Networking"
- TID-221: Authentication Bypass By Message Replay
- TID-222: Critical System Service May Be Disabled
- TID-310: Remotely Accessible Unauthenticated Services
- TID-316: Incorrect Certificate Verification Allows Authentication Bypass
- TID-317: Predictable Cryptographic Key
- TID-318: Insecure Cryptographic Implementation
- TID-401: Undocumented Protocol Features
- TID-404: Remotely Triggerable Deadlock/DoS
- TID-405: Network Stack Resource Exhaustion
- TID-406: Unauthorized Messages or Connections
- TID-407: Missing Message Replay Protection
- TID-408: Unencrypted Sensitive Data Communication
- TID-410: Cryptographic Protocol Side Channel
- TID-411: Weak/Insecure Cryptographic Protocol
- TID-412: Network Routing Capability AbuseNote --pprint (default is OFF, default output is JSON) for display
Explore other commands using the CLI help
Usage: med [OPTIONS] COMMAND [ARGS]...
╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --release TEXT 2.0.1, 2.0 ... [default: 2.0.1] │
│ --loglevel -l TEXT Set the logging level (debug, info, warning, error, critical) [default: warning] │
│ --pprint --no-pprint Whether to pretty-print the output (e.g. JSON lists) [default: no-pprint] │
│ --install-completion Install completion for the current shell. │
│ --show-completion Show completion for the current shell, to copy it or customize the installation. │
│ --help Show this message and exit. │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ list-categories List the categories │
│ list-properties List properties for a certain category │
│ list-threats List threats for a certain category │
│ list-mitigations List mitigations for a certain threat │
│ threat Threat Information │
│ mitigation Mitigation Information │
│ tui Launch the TUI heatmap viewer for a given heatmap file │
│ mcp Launch the MCP server │
│ heatmap Heatmap related commands │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯You can use TUI to inspect & edit the Heatmap
# Make sure to initialize the heatmap
uvx mitre-emb3d heatmap init "Project Name" "Description of Project" --output-dir .- Above command will create
mitre-emb3d-heatmap.jsonfile in the specified output directory - All the entries in the heatmap are set to NOT_INVESTIGATED
# Show the current state (and edit) using TUI
uvx mitre-emb3d tui mitr-emb3d-heatmap.json
Clicking on Threat Entry will open a screen that presents a Form, Information about Threat & Mitigations
At the moment only STDIO is supported
For your mcp.json add the server like this
{
"servers": {
"mitre-emb3d": {
"command": "uvx",
"args": ["mitre-emb3d", "mcp"]
}
}
}
Use mcp inspector to play with the MCP Server
npx -y @modelcontextprotocol/inspector uvx mitre-emb3d mcp