Ext Ops Panel
Open dashboard
Comparison

Firewalla vs Vectra AI RUX MCP Server

Firewalla is an MCP server published by amittell. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vectra AI RUX MCP Server is an MCP server published by vectra-ai-research. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-30. 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
MarketplaceFirewallaVectra AI RUX MCP Server
Docker MCP Catalog Listed
Version: sha256:af186f868759
Forks (GitHub): 13
Pulls (Docker Hub): 31 157
Stars (Docker Hub): 0
Stars (GitHub): 39
Not marked · First seen
Listed
Version: sha256:e079ffaf48e4
Forks (GitHub): 6
Pulls (Docker Hub): 11 945
Stars (Docker Hub): 0
Stars (GitHub): 6
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

Firewalla vs Vectra AI RUX MCP Server
FactFirewallaVectra AI RUX MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)39 (better)6 (worse)
Pulls (Docker Hub) (differs)31 157 (better)11 945 (worse)
Forks (GitHub) (differs)13 (better)6 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/firewalla-mcp-server)On your machine (mcp/vectra-ai-rux-mcp-server)
Transportstdiostdio
Tools it declares (differs)2825
Environment variables it asks for (differs)12, secrets among them: 13, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/amittell/firewalla-mcp-servergithub.com/vectra-ai-research/vectra-ai-mcp-server
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

Firewalla

In its own words, on Docker MCP Catalog:

Real-time network monitoring, security analysis, and firewall management through 28 specialized tools. Access security alerts, network flows, device status, and firewall rules directly from your Firewalla device.

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.

How to run each

Firewalla As a local MCP server: Docker image

Claude Code
claude mcp add --env "FIREWALLA_MSP_TOKEN=<YOUR_FIREWALLA_MSP_TOKEN>" --transport stdio firewalla-mcp-server -- docker run -i --rm -e FIREWALLA_MSP_TOKEN mcp/firewalla-mcp-server

Requires: FIREWALLA_MSP_TOKEN (secret)

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)

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

Tools each declares

Only Firewalla declares

  • create_target_list
  • delete_target_list
  • get_active_alarms
  • get_alarm_trends
  • get_bandwidth_usage
  • get_boxes
  • get_device_status
  • get_flow_data
  • get_flow_insights
  • get_network_rules
  • get_network_rules_summary
  • get_offline_devices
Show the remaining 16
  • get_recent_flow_activity
  • get_rule_trends
  • get_simple_statistics
  • get_specific_alarm
  • get_specific_target_list
  • get_statistics_by_box
  • get_statistics_by_region
  • get_target_lists
  • pause_rule
  • resume_rule
  • search_alarms
  • search_devices
  • search_flows
  • search_rules
  • search_target_lists
  • update_target_list

Only Vectra AI RUX MCP Server declares

  • Summarize Detection
  • Visualize Entity Detections
  • create_assignment
  • create_entity_note
  • delete_assignment
  • get_account_details
  • get_assignment_detail_by_id
  • get_assignment_for_entity
  • get_detection_count
  • get_detection_details
  • get_detection_pcap
  • get_detection_summary
Show the remaining 13
  • get_host_details
  • list_assignments
  • list_assignments_for_user
  • list_detection_ids
  • list_detections_with_basic_info
  • list_detections_with_details
  • list_entities
  • list_entity_detections
  • list_lockdown_entities
  • list_platform_users
  • lookup_entity_info_by_name
  • lookup_host_by_ip
  • mark_detection_fixed

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Firewalla asks for

  • FIREWALLA_BOX_ID
  • FIREWALLA_MSP_ID
  • FIREWALLA_MSP_TOKEN (secret)
  • LOG_LEVEL
  • MCP_CACHE_ENABLED
  • MCP_CACHE_TTL
  • MCP_DEBUG_MODE
  • MCP_RATE_LIMIT_MAX_REQUESTS
  • MCP_RATE_LIMIT_WINDOW
  • MCP_READ_ONLY_MODE
  • MCP_WAVE0_ENABLED
  • NODE_ENV

Only Vectra AI RUX MCP Server asks for

  • VECTRA_BASE_URL
  • VECTRA_CLIENT_ID
  • VECTRA_CLIENT_SECRET (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Firewalla · What it can do: Vectra AI RUX MCP Server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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