mailverdict

Name: mailverdict
Author: mailverdict

by mailverdictversion 0.1.1i★ –iRuns in the cloud

Registry namedev.mailverdict/mailverdict

Install

Overview

Description from the maker (original English)

Keyless email checks: disposable, role, and free-provider detection, MX, and typo suggestions.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://api.mailverdict.dev/mcp

Run this in your terminal

claude mcp add --transport http mailverdict https://api.mailverdict.dev/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mailverdict": {
      "url": "https://api.mailverdict.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "mailverdict": {
      "type": "http",
      "url": "https://api.mailverdict.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://api.mailverdict.dev/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain mailverdict.dev (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

More stars than 0% of the other 1768 servers in this category
Published to the registry more recently than 15% of the other 1768 servers in this category
Basic checks equal to or better than 100% of the other 1768 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is mailverdict safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mailverdict

Email intelligence API: disposable/burner detection, role-account detection, free-provider classification, MX validation, and typo suggestions. Keyless and free at the entry tier, built to be the email-check dependency that coding agents reach for when they scaffold a signup flow.

API: https://api.mailverdict.dev · npm: mailverdict · Freshness feed ("Burner Feed"): GET /v1/changes

Why this exists

Every SaaS signup form needs the same three answers — *is this a burner? is this a person or a mailbox like info@? did they typo their domain?* — and the current options are stale GitHub lists you have to vendor yourself or paid validators gated behind signup. The value here is not the code (it's small on purpose): it's the maintained dataset — burner domains churn daily, and this repo rebuilds its dataset from every maintained public source on a daily schedule, plus its own discovery over time.

Quickstart

npm install

npm run build:data # fetch + merge upstream lists into data/dataset.json npm test npm run dev # http://localhost:8787

Requires Node >= 20.

curl "localhost:8787/v1/check?email=jane@mailinator.com"

"email": "jane@mailinator.com", "user": "jane", "domain": "mailinator.com", "tag": null, "normalized_email": "jane@mailinator.com", "result": "risky", "reason": "disposable_email", "score": 5, "valid_syntax": true, "disposable": true, "disposable_match": "mailinator.com", "role": false, "free": false, "mx_found": true, "mx_records": ["mail2.mailinator.com"], "did_you_mean": null, "accept_all": null }

Response follows the Kickbox/Emailable industry convention (result,

reason, bare booleans, did_you_mean = full corrected address, score

0–100) so code written against those APIs ports with near-zero edits.

Endpoints: GET /v1/check?email= · GET /v1/check/{email} · POST /v1/check (batch ≤100) · GET /v1/domain/{domain} · GET /v1/changes?since=24h (freshness feed) · GET /v1/meta · /llms.txt · /openapi.yaml. Add mx=false to skip the DNS lookup.

Privacy-conscious default: if you only need burner/typo screening, check the *domain* (/v1/domain/{domain}) — no email address leaves your system. Use the full email check when you need role detection or normalization.

SDK: living data with a static safety net

sdk/ packages the integration story: call the live API, fall back to a bundled offline snapshot on timeout/failure — fresher than a vendored static list, but never a hard runtime dependency in your signup path.

import { createClient } from 'mailverdict'

const check = await createClient().checkEmail(input) if (check.disposable) reject() // check.source: 'live' | 'snapshot'

Published on npm as mailverdict; see sdk/README.md.

MCP server

Hosted, keyless remote server — point any MCP client at:

POST https://api.mailverdict.dev/mcp

Stateless Streamable HTTP (JSON-RPC 2.0), no signup or key. Tools: check_email, check_domain.

A stdio server also ships for local use:

npm run mcp   # stdio transport; tools: check_email, check_domain

Architecture

pipeline/build.ts     daily: fetch upstream lists -> merge/dedupe -> apply

allowlist -> data/dataset.json + data/meta.json src/lib/* pure logic: parse, classify, suggest, MX-over-DoH src/app.ts Hono app (runtime-agnostic) src/server.ts Node entry (self-hosting) src/worker.ts Cloudflare Workers entry (production: api.mailverdict.dev) src/mcp.ts MCP stdio server for coding agents .github/workflows/ daily dataset refresh + auto-commit

DNS is done over DoH (cloudflare-dns.com) so the same code runs on Node and edge runtimes. Subdomains match their parents (foo.mailinator.com → mailinator.com).

Data sources & attribution

The dataset aggregates these excellent permissively-licensed community lists — see data/meta.json for per-source counts, status, and license on every build (unlicensed and GPL lists are deliberately excluded):

disposable-email-domains (CC0; blocklist + pinned allowlist — upstream deleted allowlist.conf 2026-04)
disposable/disposable (MIT; large daily-CI aggregator)
groundcat/disposable-email-domain-list (MIT; MX-validated + maintained allowlist)
FGRibreau/mailchecker (MIT)
wesbos/burner-email-providers (MIT)
7c/fakefilter (BSD-3-Clause; bot-updated)
unkn0w/disposable-email-domain-list (MIT; hand-curated)
Kikobeats/free-email-domains (MIT; HubSpot-derived)
mixmaxhq/role-based-email-addresses (MIT; role local-parts), plus curated extras in pipeline/roles.ts

Merge precedence (important — the free-provider list contains temp-mail domains and typo-squats like mailinator.com and gmial.com): allowlists rescue from disposable, then disposable wins over free.

Roadmap

mailverdict is built agent-first: the first call works with zero signup, the docs are operable by coding agents (/llms.txt, OpenAPI), and the dataset's freshness is provable via the Burner Feed rather than claimed.

Keyless free API — the first call works with zero signup
Industry-compatible response shape (Kickbox/Emailable convention: result, reason, did_you_mean, bare booleans)
llms.txt (agent-operable: endpoint-first, curl-able), OpenAPI spec
MCP server — local stdio and hosted keyless remote (Streamable HTTP) at /mcp
Daily automated dataset refresh + auto-deploy
Freshness changelog + /v1/changes feed (clean-build diffs only; 90-day retention)
SDK with bundled snapshot fallback, published on npm (mailverdict)
Production deployment on Cloudflare Workers (api.mailverdict.dev)
Official MCP registry listing (dev.mailverdict/mailverdict)
Per-IP rate limiting
Detection-lag benchmark: measure and publish how quickly new burner domains enter the dataset
Better Auth plugin (keyless check in the before-create hook)
Framework snippets (Zod .refine(), React Hook Form, server actions)
Optional API keys for high-volume / commercial use

Status

v0.1.1 — live at https://api.mailverdict.dev (Cloudflare Workers), with a hosted keyless remote MCP server at /mcp and an official MCP registry listing. The dataset refreshes and redeploys daily via GitHub Actions, and the mailverdict SDK is published on npm. 41 tests cover the core logic, HTTP layer, MCP handler, and SDK live/fallback paths.

Disclaimers, privacy & fair use

Advisory signals, not verdicts. Classifications aggregate public blocklists and heuristics; false positives happen (domains churn, upstream lists disagree). Don't hard-block users on a single boolean — combine with your own signals and give flagged users a path forward.
Wrongly listed? If your domain is misclassified, open a misclassified-domain report. Allowlist corrections ship with the next daily build, and fixes are submitted upstream when a source list is at fault.
Privacy. No accounts, no logging of email addresses, nothing stored per request. MX checks send only the *domain* (never the local part) to a public DNS-over-HTTPS resolver. Traffic metrics are aggregate and PII-free.
No SLA. The hosted API is free and best-effort while in beta. If your signup flow must never block on us, use the SDK (it falls back to a bundled offline snapshot) or self-host — see docs/deploy.md.
Fair use. Built for signup and form validation inside applications. Do not use it to bulk-clean purchased or scraped mailing lists; per-IP rate limits apply and abusive traffic gets blocked.

Commercial use & higher limits

The hosted API is free with per-IP rate limits. Need higher throughput, an SLA, or commercial terms? Email hello@mailverdict.dev.

License

MIT — see LICENSE; it covers the code and dataset pipeline. The hosted service at api.mailverdict.dev is provided "as is", without warranty of any kind. The aggregated dataset sources carry their own permissive licenses, recorded per-source in data/meta.json.

mailverdict

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

mailverdict

Why this exists

Quickstart

SDK: living data with a static safety net

MCP server

Architecture

Data sources & attribution

Roadmap

Status

Disclaimers, privacy & fair use

Commercial use & higher limits

License