Hby Hunter
Enrich a person and their company
Returns the profile of the person behind an email address, with their name, location and employment, together with their company's profile, in one call.
Description
Pass an `email` or a `linkedin_handle`; set `clearbit_format` to get a Clearbit-compatible response. A `404` means Hunter has nothing on the person, and a `451` means they asked Hunter to stop processing their data: don't use it. To enrich only the person or only a company, use `Person-Enrichment` (`GET /people/find`) or `Company-Enrichment` (`GET /companies/find`).
enrich-person-and-company.md
Enrich a person and their company
Returns the profile of the person behind an email address, with their name, location and employment, together with their company's profile, in one call.
Pass an email or a linkedin_handle; set clearbit_format to get a
Clearbit-compatible response. A 404 means Hunter has nothing on the person,
and a 451 means they asked Hunter to stop processing their data: don't use
it. To enrich only the person or only a company, use Person-Enrichment
(GET /people/find) or Company-Enrichment (GET /companies/find).
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 Combined-Enrichment.
Server URL: https://mcp.hunter.io/mcp
API (official)
- Base URL: https://api.hunter.io/v2
- Endpoint:
GET /combined/find - 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.