---
ref: tool:hunter/search-domain
name: Search a domain for emails
company: company:hunter
workflows: []
access: [mcp, api]
tags: [capability:find-work-emails, category:data-provider, has:api, has:mcp]
docs: https://hunter.io/api-documentation/v2#domain-search
updated: 2026-09-27
---

# Search a domain for emails

Returns the email addresses Hunter has found for a company domain, with each person's name, position, seniority, department and a confidence score.

Pass a `domain` (or a `company` name). Narrow the results with `department`,
`seniority`, `type` (`personal` or `generic`) or `decision_maker`, and page
through them with `limit` (10 by default) and `offset`. The response also
includes the domain's email `pattern` and whether it accepts all addresses
(`accept_all`).

## 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 `Domain-Search`.

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

### API (official)

- Base URL: https://api.hunter.io/v2
- Endpoint: `GET /domain-search`
- 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.