Ext Ops Panel
Open dashboard
Comparison

Suzieq vs InboxGuards Email Check

Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). InboxGuards Email Check is an MCP server published by api.inboxguardstest.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceSuzieqInboxGuards Email Check
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: 1.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 InboxGuards Email Check
FactSuzieqInboxGuards Email Check
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-14
Where it runs (differs)On your machine (mcp/suzieq-mcp)Remote server (api.inboxguardstest.com/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-mcpNot stated
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

Suzieq

In its own words, on Docker MCP Catalog:

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

InboxGuards Email Check

In its own words, on Official MCP Registry:

Check emails before you send, and get a $1 SPF/DKIM/DMARC fix plan for your domain. Pay per call.

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)

InboxGuards Email Check As a remote MCP server

Claude Code
claude mcp add --transport http email https://api.inboxguardstest.com/mcp

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

Only InboxGuards Email Check has a remote endpoint we check. How we check endpoints

Tools each declares

Only Suzieq has

  • run_suzieq_show
  • run_suzieq_summarize

Only InboxGuards Email Check has

  • check_email_address
  • email_fix_plan
  • pricing
  • validate_email

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (InboxGuards Email Check as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of InboxGuards Email Check publish no settings it asks for, so we do not compare settings.

What it can do: Suzieq · What it can do: InboxGuards Email Check · 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