Hby Hunter
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.
Description
Pass `domain` (or `company`) with `first_name` and `last_name` or `full_name`, or a `linkedin_handle` alone. Every email found is verified, and a search that finds nothing costs no credit. A found email is also saved to your Hunter leads unless that is turned off for the account. A `451` means the person asked Hunter to stop processing their data: don't use it.
find-email.md
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.
Pass domain (or company) with first_name and last_name or
full_name, or a linkedin_handle alone. Every email found is verified, and
a search that finds nothing costs no credit. A found email is also saved to
your Hunter leads unless that is turned off for the account. 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.
{ "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 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.