Accessibility Ai MCP server. Tools: check color contrast, suggest alt text, check heading hierarchy. Built by MEOK AI Labs.
Free
Nothing to run from here
Mitre is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for MITRE ATT&CK knowledge base - technique lookup, threat intelligence, detection coverage analysis
Quickstart
# 1 — run it from where its publisher ships it
npx -y mitre-mcp
# 2 — ask your agent something
> MCP server for MITRE ATT&CK knowledge base - technique lookup, threat intelligence, detection coverage analysis
Mitre is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
LIAll 11 servers
lidless-labs11 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Mitre as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add mitre-mcp -- npx -y mitre-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
39 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Build a technique profile from observed techniques for campaign analysis and attribution
Takes no parameters.
Example callreturns →
Get details on a known ATT&CK campaign including techniques, software, and attributed groups
Takes no parameters.
Example callreturns →
List all known ATT&CK campaigns with names, dates, and brief descriptions
Takes no parameters.
Example callreturns →
Search campaigns by keyword or by technique usage
Takes no parameters.
Example callreturns →
Get details on a data source and its components with detectable techniques
Takes no parameters.
Example callreturns →
Analyze detection coverage based on available data sources in your environment
Takes no parameters.
Example callreturns →
Get details on a known threat group/APT including techniques and software used
Takes no parameters.
Example callreturns →
Search threat groups by keyword or by technique usage
Takes no parameters.
Example callreturns →
List all known threat groups with names, aliases, and brief descriptions
Takes no parameters.
Example callreturns →
Force an update of the local ATT&CK data cache by re-downloading STIX bundles
Takes no parameters.
Example callreturns →
Get current ATT&CK data version, freshness, and object counts
Takes no parameters.
Example callreturns →
Map a security alert or observable to likely ATT&CK techniques with confidence scoring
Takes no parameters.
Example callreturns →
Find technique overlap between threat groups for attribution assistance
Takes no parameters.
Example callreturns →
Generate possible attack paths through the kill chain starting from a technique
Takes no parameters.
Example callreturns →
Get details on a mitigation and all techniques it addresses
Takes no parameters.
Example callreturns →
Get all mitigations applicable to a specific technique
Takes no parameters.
Example callreturns →
Search mitigations by keyword
Takes no parameters.
Example callreturns →
Generate an ATT&CK Navigator layer JSON for visualization. Supports coverage heatmaps, group technique overlays, campaign views, and custom technique highlighting.
Takes no parameters.
Example callreturns →
Get details on a known software, malware, or tool including techniques and associated groups
Takes no parameters.
Example callreturns →
Search software/malware by name, keyword, technique, or type
Takes no parameters.
Example callreturns →
List all ATT&CK tactics in kill-chain order
Takes no parameters.
Example callreturns →
Get details and all techniques under a specific tactic
Takes no parameters.
Example callreturns →
Get full details of a specific ATT&CK technique by its ID (e.g., T1059, T1059.001)
Takes no parameters.
Example callreturns →
Search ATT&CK techniques by keyword, tactic, platform, or data source
Takes no parameters.
Example callreturns →
Map a MISP event
Takes no parameters.
Example callreturns →
Search MISP for indicators (IOCs) related to specific ATT&CK techniques or threat groups
Takes no parameters.
Example callreturns →
Create a MISP event pre-tagged with ATT&CK techniques and threat group galaxies
Takes no parameters.
Example callreturns →
List recent MISP events with ATT&CK technique enrichment
Takes no parameters.
Example callreturns →
Get connection status for all configured SOC integrations (Wazuh, TheHive, Cortex, MISP)
Takes no parameters.
Example callreturns →
Cross-correlate ATT&CK techniques across Wazuh alerts, TheHive cases, and MISP events to find related activity
Takes no parameters.
Example callreturns →
Map Cortex analyzers to ATT&CK data sources and calculate technique detection potential
Takes no parameters.
Example callreturns →
Run Cortex analyzers on an observable and map results to ATT&CK context
Takes no parameters.
Example callreturns →
Enrich TheHive case observables with ATT&CK context. Takes a case ID and adds ATT&CK technique tags, suggested mitigations, and threat group correlations.
Takes no parameters.
Example callreturns →
Create a new TheHive case pre-populated with ATT&CK context from observed techniques
Takes no parameters.
Example callreturns →
List TheHive cases with optional ATT&CK technique filtering
Takes no parameters.
Example callreturns →
Get Wazuh manager status, agent summary, and rule statistics
Takes no parameters.
Example callreturns →
Map a Wazuh alert (by rule ID, description, or groups) to ATT&CK techniques with confidence scoring
Takes no parameters.
Example callreturns →
Analyze Wazuh rules and map them to ATT&CK technique coverage. Shows which techniques your Wazuh deployment can detect.
Takes no parameters.
Example callreturns →
Fetch recent Wazuh alerts and enrich them with ATT&CK context
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Mitre costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 97 / 100
Release 2.0.4 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest8e96e0decebbb140b352a93356c1a48a39eac9eb6f1fbe173898f1745fb44f54
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (39 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| mitre_get_technique | no tags | |
| mitre_search_techniques | no tags | |
| mitre_list_tactics | no tags | |
| mitre_get_tactic | no tags | |
| mitre_get_group | no tags | |
| mitre_search_groups | no tags | |
| mitre_list_groups | no tags | |
| mitre_get_software | no tags | |
| mitre_search_software | no tags | |
| mitre_get_mitigation | no tags | |
| mitre_mitigations_for_technique | no tags | |
| mitre_search_mitigations | no tags | |
| mitre_get_datasource | no tags | |
| mitre_detection_coverage | no tags | |
| mitre_map_alert_to_technique | no tags | |
| mitre_technique_overlap | no tags | |
| mitre_attack_path | no tags | |
| mitre_campaign_profile | no tags | |
| mitre_get_campaign | no tags | |
| mitre_list_campaigns | no tags | |
| mitre_search_campaigns | no tags | |
| mitre_navigator_layer | no tags | |
| mitre_update_data | no tags | |
| mitre_data_version | no tags | |
| mitre_wazuh_status | no tags | |
| mitre_map_wazuh_alert | no tags | |
| mitre_wazuh_rule_coverage | no tags | |
| mitre_wazuh_alerts | untrusted-input | |
| mitre_thehive_enrich | no tags | |
| mitre_thehive_create_case | no tags | |
| mitre_thehive_list_cases | no tags | |
| mitre_cortex_analyzer_coverage | no tags | |
| mitre_cortex_run_analyzers | no tags | |
| mitre_misp_event_to_attack | no tags | |
| mitre_misp_search_indicators | no tags | |
| mitre_misp_create_event | no tags | |
| mitre_misp_list_events | no tags | |
| mitre_soc_status | no tags | |
| mitre_cross_correlate | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8e96e0decebbb140
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 2.0.4 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
2.0.4
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Mitre in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.