Inspektor Gadget vs scan.mx Email Diagnostics
Inspektor Gadget is an MCP server published by inspektor-gadget. Marketplaces we read that list it: 1 (Docker MCP Catalog). scan.mx Email Diagnostics is an MCP server published by scan.mx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  Inspektor Gadget |  scan.mx Email Diagnostics |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a54c99a50a81 Forks (GitHub): 6 Pulls (Docker Hub): 13 326 Stars (Docker Hub): 2 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.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 | Inspektor Gadget | scan.mx Email Diagnostics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 13 326 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/inspektor-gadget) | Remote server (api.scan.mx/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 37 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/inspektor-gadget/ig-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 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
Inspektor Gadget
AI interface to troubleshoot and observe Kubernetes/Container workloads.
scan.mx Email Diagnostics
Email deliverability check: MX, SPF, DKIM, DMARC, blacklists, MTA-STS, DNSSEC, BIMI. Graded, no key.
How to run each
Inspektor Gadget As a local MCP server: Docker image
claude mcp add --transport stdio inspektor-gadget -- docker run -i --rm mcp/inspektor-gadgetscan.mx Email Diagnostics As a remote MCP server
claude mcp add --transport http diagnostics https://api.scan.mx/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only scan.mx Email Diagnostics has a remote endpoint we check. How we check endpoints
Tools each declares
Only Inspektor Gadget has
gadget_advise_networkpolicygadget_advise_seccompgadget_audit_seccompgadget_bpfstatsgadget_deadlockgadget_fdpassgadget_fsnotifygadget_profile_blockiogadget_profile_cpugadget_profile_qdisc_latencygadget_profile_tcprttgadget_snapshot_process
Show the remaining 25
gadget_snapshot_socketgadget_tcpdumpgadget_top_blockiogadget_top_filegadget_top_processgadget_top_tcpgadget_trace_bindgadget_trace_capabilitiesgadget_trace_dnsgadget_trace_execgadget_trace_fsslowergadget_trace_lsmgadget_trace_mallocgadget_trace_mountgadget_trace_oomkillgadget_trace_opengadget_trace_signalgadget_trace_snigadget_trace_sslgadget_trace_tcpgadget_trace_tcpdropgadget_trace_tcpretransgadget_traceloopig_deployig_gadgets
Only scan.mx Email Diagnostics has
check_bimicheck_blacklistcheck_dkimcheck_dmarccheck_dnsseccheck_domaincheck_mta_stscheck_mxcheck_spf
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (scan.mx Email Diagnostics as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Inspektor Gadget · What it can do: scan.mx Email Diagnostics · 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.