Skip to main content
ClaudeWave

Email verification for AI agents: send, hold or kill with the reason. CLI, MCP server and hosted API.

MCP ServersOfficial Registry2 stars0 forksTypeScriptMITUpdated today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 9/14/2026
Install in Claude Code / Claude Desktop
Method: NPX · mxprobe
Claude Code CLI
claude mcp add mxprobe -- npx -y mxprobe
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "mxprobe": {
      "command": "npx",
      "args": ["-y", "mxprobe"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers overview

# MX Probe

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.

- Site and docs: https://mxprobe.dev
- API: https://api.mxprobe.dev (it describes itself on `GET /`). OpenAPI: https://mxprobe.dev/openapi.json. For agents: https://mxprobe.dev/llms.txt
- npm: [`mxprobe`](https://www.npmjs.com/package/mxprobe) (CLI + MCP server), [`mxprobe-core`](https://www.npmjs.com/package/mxprobe-core) (the engine)

```bash
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
```

```json
{
  "email": "hello@example.com",
  "action": "send",
  "verdict": "OK",
  "reason": "mailbox accepted by aspmx.l.google.com",
  "checks": { "syntax": true, "mx": "aspmx.l.google.com", "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.

## Layout

| 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 | signup | balance | buy | mcp`. Also exports `createClient`. |
| `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. |

## Develop

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.

```bash
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`).

## Pricing

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.
ai-agentscliemailemail-validationemail-verificationmcpmcp-serversmtptypescript

What people ask about mxprobe

What is andrewchmr/mxprobe?

+

andrewchmr/mxprobe is mcp servers for the Claude AI ecosystem. Email verification for AI agents: send, hold or kill with the reason. CLI, MCP server and hosted API. It has 2 GitHub stars and its last recorded update is dated 2026-09-13.

How do I install mxprobe?

+

You can install mxprobe by cloning the repository (https://github.com/andrewchmr/mxprobe) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is andrewchmr/mxprobe safe to use?

+

Our security agent has analyzed andrewchmr/mxprobe and assigned a Trust Score of 95/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.

Who maintains andrewchmr/mxprobe?

+

andrewchmr/mxprobe is maintained by andrewchmr. The last recorded GitHub activity is dated 2026-09-13, with 0 open issues.

Are there alternatives to mxprobe?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy mxprobe to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: andrewchmr/mxprobe
[![Featured on ClaudeWave](https://claudewave.com/api/badge/andrewchmr-mxprobe)](https://claudewave.com/repo/andrewchmr-mxprobe)
<a href="https://claudewave.com/repo/andrewchmr-mxprobe"><img src="https://claudewave.com/api/badge/andrewchmr-mxprobe" alt="Featured on ClaudeWave: andrewchmr/mxprobe" width="320" height="64" /></a>

More MCP Servers

mxprobe alternatives