dev.mxprobe/mxprobe is an MCP server that email verification for AI agents: send, hold or kill with the reason. Signup and credits by API. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 61/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"dev-mxprobe-mxprobe": {
"args": [
"-y",
"mxprobe"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Email verification for AI agents: send, hold or kill with the reason. Signup and credits by API.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked mxprobe against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / communication
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
MCP Security Weekly
Get CVE alerts and security updates for dev.mxprobe/mxprobe and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Email verification for AI agents. One call returns send, hold or kill
for an address, with the reason. Signup and credits happen by API too, so an
outreach agent can provision itself. No form, no CAPTCHA, no dashboard.
GET /). OpenAPI: https://mxprobe.dev/openapi.json. For agents: https://mxprobe.dev/llms.txtmxprobe (CLI + MCP server), mxprobe-core (the engine)npx mxprobe check hello@example.com # free DNS tier, local, no key
npx mxprobe check --hosted hello@example.com # survivors go to the hosted SMTP probe
claude mcp add mxprobe -- npx -y mxprobe mcp # the MCP server
One click: Cursor · VS Code ·
LM Studio. In Claude Code the same server also comes as a plugin:
/plugin marketplace add andrewchmr/mxprobe, then /plugin install mxprobe@mxprobe.
{
"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 }
}
action is send, hold or kill; verdict is OK, WEAK or DEAD. A
hold never becomes a kill on a refusal, a greylist or a catch-all. Only a
5xx that names the mailbox kills.
| Path | What |
|---|---|
packages/core | The engine: DNS tier, SMTP probe, the verdict contract and the API's wire types. Zero dependencies. |
packages/cli | `npx mxprobe check |
server | The hosted API: node:http + node:sqlite, Stripe Checkout, Resend, Telegram. |
site | The landing page, static. |
deploy | Caddyfile, systemd units, the install script and the runbook. |
Everything is TypeScript (strict, ESM). Each package compiles its src/ to
dist/ with tsc -b; the published packages ship dist/ only. mxprobe and
the server import mxprobe-core through the workspace link to its dist/,
so pnpm build at the root (which runs the packages in dependency order) must
come before a single package's test or typecheck. Tests are .ts files
that Node runs directly with its built-in type stripping.
pnpm install
pnpm build # tsc -b in each package, core first
pnpm test # builds, then: fake resolver, fake SMTP server, in-memory SQLite. No network.
pnpm typecheck # the sources and the tests, without emitting
pnpm test:live # the DNS tier against the real network
pnpm check a@b.com # the CLI from this checkout
cp server/.env.example server/.env && pnpm dev:server
Node 22.18 or newer (24 recommended) to develop and to run the tests; the
compiled engine and CLI run on Node 20, the server on 22.13 or newer
(node:sqlite).
100 checks free at signup, then 9 USD per 10,000, one payment, credits never expire. Addresses are logged for 24 hours for debugging and then deleted.
MIT.