Ext Ops Panel
Open dashboard
Comparison

zoho-mail-health-check vs NoBounce Email Validation

zoho-mail-health-check is a plugin bundle for AI coding tools published by MSApps-Mobile. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). NoBounce Email Validation is an MCP server published by notprathap. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacezoho-mail-health-checkNoBounce Email Validation
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

zoho-mail-health-check vs NoBounce Email Validation
Factzoho-mail-health-checkNoBounce Email Validation
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (nobounceapi.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/msapps-mobile/claude-pluginsgithub.com/notprathap/nobounce-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-15
Endpoint at the last check (differs)no remote endpoint we checkResponded 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

zoho-mail-health-check

In its own words, on Claude Code: claude-plugins-community:

Daily health check plugin for Zoho Mail accounts. Verifies that mail accounts are reachable, reads recent inbox messages, sends test emails, and saves a structured pass/fail report to the workspace. Designed for automated daily monitoring of business email accounts.

NoBounce Email Validation

In its own words, on Official MCP Registry:

Real-time single and bulk email validation (syntax, MX, 5,000+ disposable domains, SMTP).

How to run each

zoho-mail-health-check As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install zoho-mail-health-check@claude-community

NoBounce Email Validation As a remote MCP server

Claude Code
claude mcp add --transport http nobounce-mcp https://nobounceapi.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

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

Only NoBounce Email Validation has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: zoho-mail-health-check · What it can do: NoBounce Email Validation · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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