# MailProbe

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

- name: dev.mailprobe/mailprobe
- version: 1.1.1
- connection class: R1 (autonomous)
- trust: 96/100
- quality: 95/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/dev.mailprobe%2Fmailprobe
- tools: https://api.protogrid.dev/v1/servers/dev.mailprobe%2Fmailprobe/tools

**An agent can connect on its own if it already holds `api_key`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "mailprobe": {
      "type": "http",
      "url": "https://mailprobe.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${api_key}"
      }
    }
  }
}
```

Placeholders to fill: `${api_key}`.

## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% +updated-9d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 95/100 (strong)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 3600000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_credits (destructiveHint, idempotentHint); verify_emails (destructiveHint, idempotentHint)
- pass `tools.token_cost`: about 310 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: 100 (weight 15)

- pass `deps.known_vulns`: no known advisory in 1 resolved packages
- n/a `deps.mcp_sdk_version`: the official MCP SDK is not in the dependency graph
- pass `deps.resolvable`: mailprobe-mcp@1.1.1 resolved: 1 packages

- tools: 2, about 310 tokens to load them all
- tool set hash: 69225f0306995d208ef709385d9e0ebb
- badge: [![protogrid quality](https://protogrid.dev/badge/dev.mailprobe/mailprobe.svg)](https://protogrid.dev/servers/dev.mailprobe/mailprobe)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Dependencies

- npm mailprobe-mcp@1.1.1: resolved, 0 dependencies

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0.

## Remotes

- https://mailprobe.dev/mcp (streamable-http, auth api_key ${api_key}, reachable true, uptime30d 1)

## Packages

- npm mailprobe-mcp@1.1.1 secrets: MAILPROBE_API_KEY

## Tools (2)

- `get_credits`: Returns the number of verification credits left on the MailProbe account that owns the API key. Reading the balance uses no credit.
- `verify_emails`: 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.