Hby Hunter
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.
Description
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`).
search-domain.md
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.
{ "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.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.