---
ref: tool:hunter/find-email
name: "Find a person's email"
company: company:hunter
workflows: [workflow:referral-reply-leads]
access: [mcp, api]
tags: [capability:find-work-emails, category:data-provider, has:api, has:mcp]
docs: https://hunter.io/api-documentation/v2#email-finder
updated: 2026-09-29
---

# Find a person's email

Returns the most likely work email for a person from their name and company domain or LinkedIn handle, with a confidence score, its verification status and the public sources.

Note: A search that finds nothing costs no credit; a found email is saved to your Hunter leads unless that is turned off. A `451` means the person asked Hunter to stop processing their data: don't use it.

## 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-Finder`.

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

### API (official)

- Base URL: https://api.hunter.io/v2
- Endpoint: `GET /email-finder`
- 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 anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.