Vectra AI RUX MCP Server vs IntentFence Agent Action Firewall
Vectra AI RUX MCP Server is an MCP server published by vectra-ai-research. Marketplaces we read that list it: 1 (Docker MCP Catalog). IntentFence Agent Action Firewall is an MCP server published by razel369. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  Vectra AI RUX MCP Server |  IntentFence Agent Action Firewall |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:e079ffaf48e4 Forks (GitHub): 6 Pulls (Docker Hub): 12 104 Stars (Docker Hub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.16.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | Vectra AI RUX MCP Server | IntentFence Agent Action Firewall |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 12 104 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/vectra-ai-rux-mcp-server) | Remote server (agentpass-protocol.rmalka06.chatgpt.site/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 25 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/vectra-ai-research/vectra-ai-mcp-server | github.com/razel369/intentfence |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 26 h ago |
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
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.
IntentFence Agent Action Firewall
Fail-closed action authorization, MCP risk scanning, x402 checks, and signed receipts.
How to run each
Vectra AI RUX MCP Server As a local MCP server: Docker image
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-serverRequires: VECTRA_CLIENT_SECRET (secret)
IntentFence Agent Action Firewall As a remote MCP server
claude mcp add --transport http intentfence https://agentpass-protocol.rmalka06.chatgpt.site/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only IntentFence Agent Action Firewall has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of IntentFence Agent Action Firewall publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of IntentFence Agent Action Firewall 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: IntentFence Agent Action Firewall · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.