Ext Ops Panel
Open dashboard
Comparison

Suzieq vs Email Address Check (syntax, MX, disposable, SPF/DMARC)

Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). Email Address Check (syntax, MX, disposable, SPF/DMARC) is an MCP server published by pcp183. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceSuzieqEmail Address Check (syntax, MX, disposable, SPF/DMARC)
Docker MCP Catalog Listed
Version: sha256:ea9f7d06053d
Forks (GitHub): 1
Pulls (Docker Hub): 33 578
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.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

Suzieq vs Email Address Check (syntax, MX, disposable, SPF/DMARC)
FactSuzieqEmail Address Check (syntax, MX, disposable, SPF/DMARC)
Marketplaces that list it11
Stars (GitHub) (differs)4No figure on GitHub
Pulls (Docker Hub) (differs)33 578No figure on Docker Hub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/suzieq-mcp)Remote server (email-verify-production-c20c.up.railway.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/povedaaqui/suzieq-mcpgithub.com/pcp183/email-verify
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Suzieq

In its own words, on Docker MCP Catalog:

MCP Server to interact with a SuzieQ network observability instance via its REST API.

Email Address Check (syntax, MX, disposable, SPF/DMARC)

In its own words, on Official MCP Registry:

Check email addresses for syntax, MX and disposable domains. $0.0015/call via x402.

How to run each

Suzieq As a local MCP server: Docker image

Claude Code
claude mcp add --env "SUZIEQ_API_KEY=<YOUR_SUZIEQ_API_KEY>" --transport stdio suzieq -- docker run -i --rm -e SUZIEQ_API_KEY mcp/suzieq-mcp

Requires: SUZIEQ_API_KEY (secret)

Email Address Check (syntax, MX, disposable, SPF/DMARC) As a remote MCP server

Claude Code
claude mcp add --transport http email-verify https://email-verify-production-c20c.up.railway.app/mcp

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

Tools each declares

The marketplaces of Email Address Check (syntax, MX, disposable, SPF/DMARC) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Email Address Check (syntax, MX, disposable, SPF/DMARC) publish no settings it asks for, so we do not compare settings.

What it can do: Suzieq · What it can do: Email Address Check (syntax, MX, disposable, SPF/DMARC) · 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.

Where the data comes from: how the catalog is built