Elasticsearch vs InboxGuards Email Check
Elasticsearch is an MCP server published by elastic. 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-16. 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 |  Elasticsearch | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9c978b8277e3 Forks (GitHub): 161 Pulls (Docker Hub): 45 674 Stars (Docker Hub): 17 Stars (GitHub): 719 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
| Fact | Elasticsearch | InboxGuards Email Check |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 719 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 45 674 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 161 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/elasticsearch) | Remote server (api.inboxguardstest.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/elastic/mcp-server-elasticsearch | Not stated |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 17 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
Elasticsearch
Interact with your Elasticsearch indices through natural language conversations.
InboxGuards Email Check
Check emails before you send, and get a $1 SPF/DKIM/DMARC fix plan for your domain. Pay per call.
How to run each
Elasticsearch As a local MCP server: Docker image
claude mcp add --env "ES_API_KEY=<YOUR_ES_API_KEY>" --transport stdio elasticsearch -- docker run -i --rm -e ES_API_KEY mcp/elasticsearchRequires: ES_API_KEY (secret)
InboxGuards Email Check As a remote MCP server
claude mcp add --transport http email https://api.inboxguardstest.com/mcpCommands 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 Elasticsearch has
esqlget_mappingsget_shardslist_indicessearch
Only InboxGuards Email Check has
check_email_addressemail_fix_planpricingvalidate_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: Elasticsearch · 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.