Ext Ops Panel
Open dashboard
Comparison

Vectra AI RUX MCP Server vs incident-io

Vectra AI RUX MCP Server is an MCP server published by vectra-ai-research. Marketplaces we read that list it: 1 (Docker MCP Catalog). incident-io is a plugin bundle for AI coding tools published by incident-io. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). 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
MarketplaceVectra AI RUX MCP Serverincident-io
Docker MCP Catalog Listed
Version: sha256:e079ffaf48e4
Forks (GitHub): 6
Pulls (Docker Hub): 12 048
Stars (Docker Hub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 1.20261009.666
Forks (GitHub): 1
Stars (GitHub): 3
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

Vectra AI RUX MCP Server vs incident-io
FactVectra AI RUX MCP Serverincident-io
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)3 (worse)
Pulls (Docker Hub) (differs)12 048No figure on Docker Hub
Forks (GitHub) (differs)6 (better)1 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/vectra-ai-rux-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)25Not published
Environment variables it asks for (differs)3, secrets among them: 1Not published
LicenceMITMIT
Repository (differs)github.com/vectra-ai-research/vectra-ai-mcp-servergithub.com/incident-io/skills
Changes in the last 7 days00
First seen2026-10-112026-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

Vectra AI RUX MCP Server

In its own words, on Docker MCP Catalog:

Vectra AI MCP Server - An MCP server that connects AI assistants & agents to the Vectra AI security platform, enabling intelligent threat analysis and automated incident response.

incident-io

In its own words, on Copilot CLI: github/awesome-copilot:

Official incident.io plugins for AI agents: skills for working with [incident.io](https://incident.io/) — incidents, on-call, and investigations — and for authoring the operational content our platform draws on.

How to run each

Vectra AI RUX MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --env "VECTRA_CLIENT_SECRET=<YOUR_VECTRA_CLIENT_SECRET>" --transport stdio vectra-ai-rux-mcp-server -- docker run -i --rm -e VECTRA_CLIENT_SECRET mcp/vectra-ai-rux-mcp-server

Requires: VECTRA_CLIENT_SECRET (secret)

incident-io

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.

Tools each declares

The marketplaces of incident-io publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of incident-io publish no settings it asks for, so we do not compare settings.

What it can do: Vectra AI RUX MCP Server · What it can do: incident-io · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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