Vectra AI RUX MCP Server vs VerifyPulse: email deliverability checks
Vectra AI RUX MCP Server is an MCP server published by vectra-ai-research. Marketplaces we read that list it: 1 (Docker MCP Catalog). VerifyPulse: email deliverability checks is an MCP server published by MohDev212. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Vectra AI RUX MCP Server | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:e079ffaf48e4 Forks (GitHub): 6 Pulls (Docker Hub): 11 945 Stars (Docker Hub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.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
| Fact | Vectra AI RUX MCP Server | VerifyPulse: email deliverability checks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 11 945 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (mcp/vectra-ai-rux-mcp-server) | Remote server (verifypulse-seven.vercel.app/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/mohdev212/verifypulse |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days 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.
VerifyPulse: email deliverability checks
Daily SPF, DKIM, DMARC and MX monitoring with webhook alerts, plus free sending-domain audits.
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)
VerifyPulse: email deliverability checks As a remote MCP server
claude mcp add --transport http verifypulse https://verifypulse-seven.vercel.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only VerifyPulse: email deliverability checks has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of VerifyPulse: email deliverability checks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of VerifyPulse: email deliverability checks 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: VerifyPulse: email deliverability checks · 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.