Ext Ops Panel
Open dashboard
Comparison

Bulk Email Verifier & Validator vs io.github.mrfentmen/disify-mcp

Bulk Email Verifier & Validator is an MCP server published by monietools. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/disify-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceBulk Email Verifier & Validatorio.github.mrfentmen/disify-mcp
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
Not marked · First seen
Listed
Version: 1.0.2
Downloads/month (npm): 1 245
Downloads/week (npm): 246
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

Bulk Email Verifier & Validator vs io.github.mrfentmen/disify-mcp
FactBulk Email Verifier & Validatorio.github.mrfentmen/disify-mcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (last published figure)No figure on GitHub
Forks (GitHub) (differs)0 (last published figure)No figure on GitHub
Last release (differs)Not published2026-10-17
Where it runs (differs)Remote server (mcp.apify.com)On your machine (disify-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/monietools/monie-toolsgithub.com/mrfentmen/premium-mcps
Changes in the last 7 days (differs)23
First seen (differs)2026-10-192026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

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

Bulk Email Verifier & Validator

In its own words, on Official MCP Registry:

Check emails for valid syntax, MX records, disposable and role addresses and typos. No SMTP check.

io.github.mrfentmen/disify-mcp

In its own words, on Official MCP Registry:

Email validation from the public Disify API. No key required.

How to run each

Bulk Email Verifier & Validator

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: Authorization header

io.github.mrfentmen/disify-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio disify-mcp -- npx -y disify-mcp

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

Only Bulk Email Verifier & Validator 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

Neither one's marketplaces publish the settings it asks for.

What it can do: Bulk Email Verifier & Validator · What it can do: io.github.mrfentmen/disify-mcp · Compare two other plugins

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