---
ref: tool:hunter/verify-email
name: Verify an email address
company: company:hunter
workflows: []
access: [mcp, api]
tags: [capability:verify-emails, category:data-provider, has:api, has:mcp]
docs: https://hunter.io/api-documentation/v2#email-verifier
updated: 2026-09-27
---

# Verify an email address

Checks whether an email address is deliverable and returns its status (valid, invalid, accept_all, webmail, disposable or unknown), a score and the checks behind it.

Pass the `email`. A verification that runs past 20 seconds returns `202`:
call again with the same email until the result arrives, which still counts
as one request. Read `status`; the older `result` field is deprecated. A
verification costs half a credit, and a verified email is also saved to your
Hunter leads unless that is turned off for the account.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "hunter": { "url": "https://mcp.hunter.io/mcp" } } }
```

Call the MCP tool `Email-Verifier`.

Server URL: https://mcp.hunter.io/mcp

### API (official)

- Base URL: https://api.hunter.io/v2
- Endpoint: `GET /email-verifier`
- Auth: send the header `X-API-Key: $HUNTER_API_KEY`
- Get a key: https://hunter.io/api-keys
- Docs: https://hunter.io/api-documentation/v2

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.