# MailProbe (npm · mailprobe-mcp)

Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes.

- Trust score: 92/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mailprobe.dev`: 90/100, [markdown](https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe.md), [page](https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe)
- npm · `mailprobe-mcp`: 92/100 (this document), [markdown](https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe-mcp.md), [page](https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe-mcp)

## Channel facts

- Registry: `npm`
- Package: `mailprobe-mcp`
- Version: `1.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to MailProbe/mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 84/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 290 tokens (~145/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the MailProbe MCP server?

MailProbe runs locally as an npm package, launched with npx -y mailprobe-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dev-mailprobe-mailprobe -- npx -y mailprobe-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-mailprobe-mailprobe": {
      "command": "npx",
      "args": [
        "-y",
        "mailprobe-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-mailprobe-mailprobe": {
      "command": "npx",
      "args": [
        "-y",
        "mailprobe-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-mailprobe-mailprobe -- npx -y mailprobe-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-mailprobe-mailprobe": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mailprobe-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-mailprobe-mailprobe --command npx --arg -y --arg mailprobe-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-mailprobe-mailprobe:
    command: "npx"
    args: ["-y", "mailprobe-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-mailprobe-mailprobe": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mailprobe-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-mailprobe-mailprobe -t stdio -c npx -a -y mailprobe-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-mailprobe-mailprobe": {
      "command": "npx",
      "args": [
        "-y",
        "mailprobe-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 91, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 76, −15)

- [security regression] Malware scan: pass → unverified
- [security] The attested source repository moved: jamalofski/mailprobe-mcp → MailProbe/mcp
- [functional] Package version: 1.1.1 → 1.1.2

### 2026-11-01 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `verify_emails` (~176 tokens)

Verify Email Addresses

Checks whether email addresses exist and can receive mail, in real time and without sending anything. Returns one result per address, in input order. Act on `status`: `valid` is safe to send, `invalid` must not be used, `risky` is accepted but uncertain (catch-all domain, role or disposable address, provider that blocks probing) and `unknown` could not be determined. `score` is a 0-100 confidence value, `reason` explains a verdict that is not plainly deliverable and `did_you_mean` suggests a fix for a likely typo. One credit per address actually probed: duplicates and malformed addresses are free. At most 20 addresses per call: split a longer list into several calls.

Input parameters:

- `emails` (array, required): Email addresses to verify, 1 to 20.

### `get_credits` (~34 tokens)

Get Credit Balance

Returns the number of verification credits left on the MailProbe account that owns the API key. Reading the balance uses no credit.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe-mcp#diagnostics

## Score history

- 2026-11-05: 92
- 2026-11-04: 92
- 2026-11-03: 91
- 2026-11-02: 76
- 2026-11-01: 91
- 2026-10-31: 90
- 2026-10-30: 90
- 2026-10-29: 89
- 2026-10-28: 89
- 2026-10-27: 88
- 2026-10-26: 88
- 2026-10-25: 87
- 2026-10-24: 87
- 2026-10-23: 86
- 2026-10-22: 86
- 2026-10-21: 83
- 2026-10-20: 83
- 2026-10-19: 83
- 2026-10-18: 83
- 2026-10-17: 83
- 2026-10-16: 83
- 2026-10-15: 83
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 49

## Common questions

### What is the MailProbe MCP server?

MailProbe is an MCP server listed in the public MCP registry as dev.mailprobe/mailprobe. Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes. This page covers its npm package (mailprobe-mcp).

### Is the MailProbe MCP server safe to use?

MailProbe scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MailProbe MCP server expose?

MailProbe exposes 2 tools: verify_emails, get_credits. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.

### Is the MailProbe MCP server still maintained?

MailProbe is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the MailProbe MCP server under?

MailProbe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mailprobe-mcp
- Socket report: https://socket.dev/npm/package/mailprobe-mcp
- Repository: https://github.com/mailprobe/mcp
- Website: https://mailprobe.dev/api-docs/#mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-mailprobe-mailprobe/mailprobe-mcp