How do I install MX Probe?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does MX Probe need an API key?

The publisher lists these environment variables: MXPROBE_API_KEY.

What transport does MX Probe use?

MX Probe runs locally over stdio.

When was MX Probe last checked?

Last checked 2026-11-11. Email verification for AI agents: send, hold or kill with the reason. Signup and credits by API.

MX Probe MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

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.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1MXPROBE_API_KEY=<secret> claude mcp add dev.mxprobe-mxprobe -- npx -y mxprobe@0.2.8

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "dev.mxprobe-mxprobe": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "MXPROBE_API_KEY": "<secret>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.2.8
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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 (CLI + MCP server), mxprobe-core (the engine)

npx mxprobe check [email protected]          # free DNS tier, local, no key
npx mxprobe check --hosted [email protected] # 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": "[email protected]",
  "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
`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.

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 [email protected]              # 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.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install MX Probe?

Does MX Probe need an API key?

What transport does MX Probe use?

When was MX Probe last checked?

Documentation

MX Probe

Layout

Develop

Pricing