Ext Ops Panel
Open dashboard
Comparison

Rösti Threat Intel vs Malware Patrol Threat Intelligence MCP server

Rösti Threat Intel is an MCP server published by rosti.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Malware Patrol Threat Intelligence MCP server is an MCP server published by AndreC10002. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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

Where each is published
MarketplaceRösti Threat IntelMalware Patrol Threat Intelligence MCP server
Official MCP Registry Listed
Version: 0.2.1
No figure published
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

Rösti Threat Intel vs Malware Patrol Threat Intelligence MCP server
FactRösti Threat IntelMalware Patrol Threat Intelligence MCP server
Marketplaces that list it11
Last release (differs)2026-11-05Not published
Where it runs (differs)Remote server (mcp.rosti.dev/mcp)Remote server (mcp.malwarepatrol.net/v1)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
RepositoryNot statedNot stated
Changes in the last 7 days (differs)30
First seen (differs)2026-11-042026-10-11
Endpoint at the last check (differs)Responded 15 h agoStatus out of date: last check 2 days ago returned HTTP 307

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

Rösti Threat Intel

In its own words, on Official MCP Registry:

Look up IOCs and search threat-intel reports, YARA rules, MITRE ATT&CK ids and CVEs from rosti.dev

Malware Patrol Threat Intelligence MCP server

In its own words, on Official MCP Registry:

Our MCP Server connects AI workflows to current, curated cyber threat intelligence

How to run each

Rösti Threat Intel As a remote MCP server

Claude Code
claude mcp add --transport http rosti https://mcp.rosti.dev/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

Malware Patrol Threat Intelligence MCP server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of Rösti Threat Intel responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Rösti Threat Intel · What it can do: Malware Patrol Threat Intelligence MCP server · 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.

Where the data comes from: how the catalog is built