Lets an AI client verify email addresses by returning a verdict to send, hold, or kill based on mailbox existence and server response.
Also known as andrewchmr/mxprobe, mxprobe
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.8
- Last commit
- Nov 13, 2026
- License
- MIT
What is MX Probe MCP?
MX Probe lets an AI client verify email addresses by returning a verdict to send, hold, or kill based on mailbox existence and server response.
Summary generated from the project's README
About MX Probe MCP server
MX Probe provides email verification specifically designed for AI agents and clients. It returns a clear verdict of send, hold, or kill for any given address based on mailbox existence and server responses. Developers can use the free DNS tier which runs locally on their machine without an API key, or they can opt for the hosted SMTP probe service. The hosted tier costs 9 USD per 10,000 checks and requires an account and API key obtained through the signup command.
This MCP server runs via stdio and can be integrated into clients like Claude, Cursor, VS Code, or LM Studio. It provides specific tools including verify_email, verify_batch, signup, balance, and buy_credits. When a key is configured, the verify tools perform mailbox probing on the hosted tier, while running without a key defaults to the local DNS tier. Users can also manage their usage and purchase credits directly through the server tools.
What you can do with it
- 1Verify individual email addressesAn AI agent can check if a specific email address is valid before attempting to send a message.
- 2Process multiple addresses at onceA developer can instruct an AI to validate a list of email addresses using the batch verification tool.
- 3Manage verification creditsA user can check their remaining balance or purchase more credits through the MCP interface.
- 4Automate email safety decisionsAn AI can decide whether to immediately send an email, hold it for manual review, or discard it entirely.
Written from the project's README. Every use case is checked against a quote from it.
How to install MX Probe MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall MX Probe MCP in Claude Code
$ claude mcp add --env 'MXPROBE_API_KEY=<YOUR_MXPROBE_API_KEY>' mxprobe -- npx -y mxprobeInstall MX Probe MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mxprobe": {
"command": "npx",
"args": [
"-y",
"mxprobe"
],
"env": {
"MXPROBE_API_KEY": "<YOUR_MXPROBE_API_KEY>"
}
}
}
}Install MX Probe MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mxprobe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mxprobe"
],
"env": {
"MXPROBE_API_KEY": "<YOUR_MXPROBE_API_KEY>"
}
}
}
}Install MX Probe MCP in VS Code CLI
$ code --add-mcp '{"name":"mxprobe","type":"stdio","command":"npx","args":["-y","mxprobe"],"env":{"MXPROBE_API_KEY":"<YOUR_MXPROBE_API_KEY>"}}'Install MX Probe MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mxprobe": {
"command": "npx",
"args": [
"-y",
"mxprobe"
],
"env": {
"MXPROBE_API_KEY": "<YOUR_MXPROBE_API_KEY>"
}
}
}
}Install MX Probe MCP in Codex
$ codex mcp add mxprobe --env 'MXPROBE_API_KEY=<YOUR_MXPROBE_API_KEY>' -- npx -y mxprobeInstall MX Probe MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mxprobe] command = "npx" args = ["-y", "mxprobe"] [mcp_servers.mxprobe.env] MXPROBE_API_KEY = "<YOUR_MXPROBE_API_KEY>"
Install MX Probe MCP in Gemini CLI
$ gemini mcp add -s user -e 'MXPROBE_API_KEY=<YOUR_MXPROBE_API_KEY>' mxprobe npx -- -y mxprobeInstall MX Probe MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mxprobe": {
"command": "npx",
"args": [
"-y",
"mxprobe"
],
"env": {
"MXPROBE_API_KEY": "<YOUR_MXPROBE_API_KEY>"
}
}
}
}Configuration
MXPROBE_API_KEYSecretHosted-tier API key from POST /v1/signup or the signup tool. Without it the verify tools run the free local DNS tier.
| Name | Description | |
|---|---|---|
| MXPROBE_API_KEY | Hosted-tier API key from POST /v1/signup or the signup tool. Without it the verify tools run the free local DNS tier. | Secret |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableandrewchmr/mxprobe is public and reachablegithub.com/andrewchmr/mxprobe ↗Pass
- Package names this repository as its sourcemxprobe names andrewchmr/mxprobe as sourcenpmjs.com/package/mxprobe ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for mxprobenpmjs.com/package/mxprobe/v/0.2.8#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-05github.com/andrewchmr/mxprobe ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from mxprobePass
- No critical advisory in the package or its dependencies100 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubmxprobe
Email verification for AI agents. One call returns send, hold or kill
with the reason. The DNS tier is free and runs on your machine; the hosted
SMTP probe is 9 USD per 10,000 checks, 100 free at signup (once per IP address and company domain).
npx mxprobe check hello@example.com ops@example.org # free, local, no key
npx mxprobe signup you@company.com # a key by API, 100 free checks, saved to ~/.config/mxprobe
npx mxprobe check --hosted hello@example.com # DNS kills stay local; survivors go to the mailbox probe
npx mxprobe balance
npx mxprobe buy # a Stripe link: 9 USD per 10,000, credits never expire
npx mxprobe mcp # the MCP server on stdio
--smtp probes the mailbox from your own machine instead. It needs outbound
port 25, which most laptops and clouds block. The probe says EHLO with this
machine's host name and MAIL FROM:<>, so it names no domain; --helo (best:
the reverse DNS name of your IP) and --from change them.
MCP
claude mcp add mxprobe -- npx -y mxprobe mcp
One click: Cursor · VS Code ·
LM Studio. In Claude Code, as a plugin:
/plugin marketplace add andrewchmr/mxprobe, then /plugin install mxprobe@mxprobe.
Any client: {"mcpServers":{"mxprobe":{"command":"npx","args":["-y","mxprobe","mcp"]}}}
Tools: verify_email, verify_batch, signup, balance, buy_credits.
With a key configured, verify_* probe the mailbox on the hosted tier; without
one they run the free DNS tier. Set MXPROBE_API_KEY to use a key from the
environment.
Verdict
{
"email": "hello@example.com",
"action": "send",
"verdict": "OK",
"reason": "mailbox accepted by aspmx.l.google.com",
"checks": { "syntax": true, "mx": "aspmx.l.google.com", "provider": "google_workspace", "smtp": "accepted", "catch_all": false }
}
send: the mail server accepted the mailbox.hold: send only with a fallback in hand. A catch-all, a forwarder, a greylist, or a server that refused the probe rather than the mailbox.kill: never send. No mail server, or the mailbox does not exist.
From Node
import { createClient, checkEmails } from "mxprobe";
const client = createClient({ apiKey: process.env.MXPROBE_API_KEY });
const { results, summary } = await checkEmails(["a@b.com"], { hosted: true, client });
Typed: Client, CheckOptions, CheckOutput and the response types come
with the package; results is VerifyResult[] from mxprobe-core.
Docs: https://mxprobe.dev. Source: https://github.com/andrewchmr/mxprobe. MIT.
MX Probe MCP questions
How do I add MX Probe MCP to Claude Code?
Run claude mcp add --env 'MXPROBE_API_KEY=<YOUR_MXPROBE_API_KEY>' mxprobe -- npx -y mxprobe in your terminal. Add --scope user to make it available in every project.
How do I add MX Probe MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How much does the hosted SMTP probe cost?
The hosted SMTP probe costs 9 USD per 10,000 checks, and you get 100 free checks upon signup.
What are the different email verdicts?
The server returns 'send' if the mail server accepted the mailbox, 'hold' for catch-alls or greylisted servers, and 'kill' if the mailbox does not exist.