io.github.aplaceforallmystuff/mcp-threatintel vs io.github.mrfentmen/mitre-attack-mcp
io.github.aplaceforallmystuff/mcp-threatintel is an MCP server published by aplaceforallmystuff. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/mitre-attack-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.aplaceforallmystuff/mcp-threatintel | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Downloads/month (npm): 266 Downloads/week (npm): 95 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 762 Downloads/week (npm): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.aplaceforallmystuff/mcp-threatintel | io.github.mrfentmen/mitre-attack-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 10 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-threatintel-server) | On your machine (@mrfentmen/mitre-attack-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 4 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/aplaceforallmystuff/mcp-threatintel | github.com/mrfentmen/mitre-attack-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.aplaceforallmystuff/mcp-threatintel
Unified threat intel - OTX, AbuseIPDB, GreyNoise, abuse.ch, Feodo Tracker
io.github.mrfentmen/mitre-attack-mcp
Search the MITRE ATT&CK enterprise knowledge base for adversary techniques and tactics.
How to run each
io.github.aplaceforallmystuff/mcp-threatintel As a local MCP server: npm package
claude mcp add --env "ABUSECH_AUTH_KEY=<YOUR_ABUSECH_AUTH_KEY>" --env "ABUSEIPDB_API_KEY=<YOUR_ABUSEIPDB_API_KEY>" --env "GREYNOISE_API_KEY=<YOUR_GREYNOISE_API_KEY>" --env "OTX_API_KEY=<YOUR_OTX_API_KEY>" --transport stdio mcp-threatintel -- npx -y mcp-threatintel-serverRequires: ABUSECH_AUTH_KEY (secret), ABUSEIPDB_API_KEY (secret), GREYNOISE_API_KEY (secret), OTX_API_KEY (secret)
io.github.mrfentmen/mitre-attack-mcp As a local MCP server: npm package
claude mcp add --transport stdio mitre-attack-mcp -- npx -y @mrfentmen/mitre-attack-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.mrfentmen/mitre-attack-mcp publish no settings it asks for, so we do not compare settings.
What it can do: io.github.aplaceforallmystuff/mcp-threatintel · What it can do: io.github.mrfentmen/mitre-attack-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.