Mitre MCP Server

mitre-mcp npm v2.0.4 Source verified

Published by lidless-labs — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for MITRE ATT&CK knowledge base - technique lookup, threat intelligence, detection coverage analysis

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • mitre_wazuh_alertsingests untrusted input
  • mitre_attack_pathno sensitive capability
  • mitre_campaign_profileno sensitive capability
  • mitre_cortex_analyzer_coverageno sensitive capability
  • mitre_cortex_run_analyzersno sensitive capability
  • mitre_cross_correlateno sensitive capability
  • mitre_data_versionno sensitive capability
  • mitre_detection_coverageno sensitive capability
  • mitre_get_campaignno sensitive capability
  • mitre_get_datasourceno sensitive capability
Show 29 more tools ↓
  • mitre_get_groupno sensitive capability
  • mitre_get_mitigationno sensitive capability
  • mitre_get_softwareno sensitive capability
  • mitre_get_tacticno sensitive capability
  • mitre_get_techniqueno sensitive capability
  • mitre_list_campaignsno sensitive capability
  • mitre_list_groupsno sensitive capability
  • mitre_list_tacticsno sensitive capability
  • mitre_map_alert_to_techniqueno sensitive capability
  • mitre_map_wazuh_alertno sensitive capability
  • mitre_misp_create_eventno sensitive capability
  • mitre_misp_event_to_attackno sensitive capability
  • mitre_misp_list_eventsno sensitive capability
  • mitre_misp_search_indicatorsno sensitive capability
  • mitre_mitigations_for_techniqueno sensitive capability
  • mitre_navigator_layerno sensitive capability
  • mitre_search_campaignsno sensitive capability
  • mitre_search_groupsno sensitive capability
  • mitre_search_mitigationsno sensitive capability
  • mitre_search_softwareno sensitive capability
  • mitre_search_techniquesno sensitive capability
  • mitre_soc_statusno sensitive capability
  • mitre_technique_overlapno sensitive capability
  • mitre_thehive_create_caseno sensitive capability
  • mitre_thehive_enrichno sensitive capability
  • mitre_thehive_list_casesno sensitive capability
  • mitre_update_datano sensitive capability
  • mitre_wazuh_rule_coverageno sensitive capability
  • mitre_wazuh_statusno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.4 latest A 97/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mitre-mcp/badge.svg)](https://mcptrustchecker.com/registry/mitre-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mitre-mcp"><img src="https://mcptrustchecker.com/registry/mitre-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mitre-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mitre-mcp --online

Use the free API → How scoring works

More in Security & Testing