Ext Ops Panel
Open dashboard
Comparison

Bulk B2B Email Verifier — DNS MX, Disposable & Catch-All Check vs Nullprint

Bulk B2B Email Verifier — DNS MX, Disposable & Catch-All Check is an MCP server published by ceadigital. Marketplaces we read that list it: 1 (Official MCP Registry). Nullprint is an MCP server published by nullprintai. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-15. 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 B2B Email Verifier — DNS MX, Disposable & Catch-All CheckNullprint
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.7
Downloads/month (PyPI): 0
Downloads/week (PyPI): 50
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.1.7
Downloads/month (PyPI): 0
Downloads/week (PyPI): 50
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

Bulk B2B Email Verifier — DNS MX, Disposable & Catch-All Check vs Nullprint
FactBulk B2B Email Verifier — DNS MX, Disposable & Catch-All CheckNullprint
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-11-11
Where it runs (differs)Remote server (ceadigital.io/mcp)On your machine (nullprint-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/nullprintai/nullprint-mcp
Changes in the last 7 days22
First seen (differs)2026-11-102026-10-11
Endpoint at the last check (differs)Responded 11 h agono 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 B2B Email Verifier — DNS MX, Disposable & Catch-All Check

In its own words, on Official MCP Registry:

Bulk verify B2B emails via Cloudflare DNS MX, SPF/DMARC, disposable check & 0-99 catch-all score.

Nullprint

In its own words, on Official MCP Registry:

Create, launch, check and drive Nullprint AI antidetect browser profiles from any MCP agent.

How to run each

Bulk B2B Email Verifier — DNS MX, Disposable & Catch-All Check As a remote MCP server

Claude Code
claude mcp add --transport http email-verifier-catch-all-validator https://ceadigital.io/mcp

Nullprint As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio nullprint-mcp -- uvx nullprint-mcp

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

Only Bulk B2B Email Verifier — DNS MX, Disposable & Catch-All Check 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 B2B Email Verifier — DNS MX, Disposable & Catch-All Check · What it can do: Nullprint · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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