Skip to main content
ClaudeWave

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

MCP ServersRegistry oficial2 estrellas0 forksTypeScriptMITActualizado 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.
Casos de uso

Resumen de MCP Servers

# 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

Lo que la gente pregunta sobre mxprobe

¿Qué es andrewchmr/mxprobe?

+

andrewchmr/mxprobe es mcp servers para el ecosistema de Claude AI. Email verification for AI agents: send, hold or kill with the reason. CLI, MCP server and hosted API. Tiene 2 estrellas en GitHub y su última actualización registrada es del 2026-09-13.

¿Cómo se instala mxprobe?

+

Puedes instalar mxprobe clonando el repositorio (https://github.com/andrewchmr/mxprobe) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar andrewchmr/mxprobe?

+

Nuestro agente de seguridad ha analizado andrewchmr/mxprobe y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene andrewchmr/mxprobe?

+

andrewchmr/mxprobe es mantenido por andrewchmr. La última actividad registrada en GitHub es del 2026-09-13, con 0 issues abiertos.

¿Hay alternativas a mxprobe?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega mxprobe en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

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>

Más MCP Servers

Alternativas a mxprobe