Ext Ops Panel
Open dashboard
Comparison

Cybersecurity Threat Intelligence MCP vs Abnormal Security MCP

Cybersecurity Threat Intelligence MCP is an MCP server published by FoundryNet. Marketplaces we read that list it: 1 (Official MCP Registry). Abnormal Security MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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
MarketplaceCybersecurity Threat Intelligence MCPAbnormal Security MCP
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.4
Forks (GitHub): 12
Stars (GitHub): 61
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

Cybersecurity Threat Intelligence MCP vs Abnormal Security MCP
FactCybersecurity Threat Intelligence MCPAbnormal Security MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub61
Forks (GitHub) (differs)No figure on GitHub12
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (cyber-intel-mcp-production.up.railway.app/mcp)On your machine (https://github.com/Servosity/msp-skills/releases/download/abnormal-v0.1.4/abnormal-mcp.mcpb)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/foundrynet/cyber-intel-mcpgithub.com/servosity/msp-skills
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-14no remote endpoint we check

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

Cybersecurity Threat Intelligence MCP

In its own words, on Official MCP Registry:

CVE search, vulnerability database, EPSS exploit prediction, KEV, IP reputation & threat feed.

Abnormal Security MCP

In its own words, on Official MCP Registry:

Abnormal Security email threats, cases, and reporting in your terminal and your AI agents.

How to run each

Cybersecurity Threat Intelligence MCP As a remote MCP server

Claude Code
claude mcp add --transport http cyber-intel-mcp https://cyber-intel-mcp-production.up.railway.app/mcp

Abnormal Security MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install abnormal@msp-skills

Requires: ABNORMAL_API_TOKEN (secret)

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

Only Cybersecurity Threat Intelligence MCP has a remote endpoint we 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

The marketplaces of Cybersecurity Threat Intelligence MCP publish no settings it asks for, so we do not compare settings.

What it can do: Cybersecurity Threat Intelligence MCP · What it can do: Abnormal Security MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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