
Find, verify and enrich professional email addresses from inside an agent, over MCP or REST.
Use Hunter when an agent needs a real, verified business email rather than a guess, and you want that inside Claude, ChatGPT, Gemini or Cursor with one connector. It is a contact-data skill, not a scraper or a full enrichment table builder. The vendor's claim of 7 million users and its published agent setup files make it the low-risk default for prospecting agents.
Verified email addresses with confidence scores delivered as MCP tools on every plan, including free.
Hunter owns a large verified email dataset and a brand sales teams already pay for; the MCP server extends an existing subscription into agents rather than selling a new one.
Main trade-off
Unpublished rate limits and Premium-only Discover paging and filters.
Outreach platform plans, monthly, with about 30% off paid yearly (hunter.io/pricing, read 11 October 2026). Free: $0, 50 credits a month, 1 connected email account, 100,000 saved leads. Starter: $49 a month ($34 a month billed yearly), 2,000 credits a month, 3 email accounts. Growth: $149 ($104 yearly), 10,000 credits a month, 10 email accounts. Scale: $299 ($209 yearly), 25,000 credits a month, 20 email accounts. Enterprise: custom. A search costs 1 credit and a verification 0.5; credits reset monthly and do not roll over; a repeated lookup of the same target is counted once per calendar month; Discover is free. API-only Data Platform packs: 1,000 search credits $50, 1,000 verification credits $11, valid 12 months. The MCP server is included on every plan.
claude plugin marketplace add hunter-io/claude-plugin && claude plugin install hunter@hunter
Hosted MCP server at https://mcp.hunter.io/mcp (Streamable HTTP; OAuth in Claude Code, Claude Desktop, ChatGPT and Gemini, X-API-Key header elsewhere, mcp-remote bridge for stdio-only clients) exposing Email Finder, Email Verifier, Domain Search, Discover, enrichment and lead tools; or REST at https://api.hunter.io/v2 with the key in an X-API-Key header.
The permissions this connector asks for, as its own documentation states them.
12 actions an agent can call. Open one for its parameters and an example.
Example call
curl -H "X-API-Key: $HUNTER_API_KEY" \ "https://api.hunter.io/v2/domain-search?domain=stripe.com&department=executive,finance&seniority=executive&limit=25"
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| domain | string | Optional | Company domain, e.g. stripe.com; required unless company is given and preferred over it. |
| company | string | Optional | Company name when the domain is unknown. |
| limit | numberdefault 10 | Optional | Maximum addresses to return. |
| offset | numberdefault 0 | Optional | Addresses to skip for paging. |
| type | string | Optional | personal or generic. |
| seniority | string | Optional | junior, senior or executive, comma-separated. |
| department | string | Optional | One or more of executive, it, finance, management, sales, legal, support, hr, marketing, communication, education, design, health, operations, product, research, consulting, administrative, procurement. |
| decision_maker | boolean | Optional | Only buying-authority contacts (true) or only the rest (false). |
| required_field | string | Optional | full_name, position and/or phone_number must be present. |
| verification_status | string | Optional | valid, accept_all and/or unknown. |
| location | object | Optional | include and exclude lists of continent, business_region, country, state or city (POST only). |
| job_titles | string | Optional | Comma-separated job titles to match. |
| aggregations | booleandefault false | Optional | Add a per-department and per-seniority breakdown in meta.aggregations. |
Returns
| Field | Type | Description |
|---|---|---|
| data.emails | array | value, type, confidence, first_name, last_name, position, seniority, department, sources and verification for each address. |
| data.pattern | string | The domain's most common address pattern, e.g. {first}. |
| meta.results | number | Total addresses available for paging. |
Example call
import os, requests
r = requests.get(
"https://api.hunter.io/v2/email-finder",
params={"domain": "reddit.com", "first_name": "Alexis", "last_name": "Ohanian", "max_duration": 15},
headers={"X-API-Key": os.environ["HUNTER_API_KEY"]},
timeout=30,
)
print(r.json()["data"]["email"], r.json()["data"]["score"])Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| domain | string | Optional | Company domain; required unless company or linkedin_handle is given. |
| company | string | Optional | Employer name if the domain is unknown. |
| linkedin_handle | string | Optional | LinkedIn profile handle as an alternative to name plus company. |
| first_name | string | Optional | Given name; required with last_name unless full_name or linkedin_handle is used. |
| last_name | string | Optional | Family name. |
| full_name | string | Optional | Full name when first and last are not separable. |
| max_duration | number | Optional | Seconds Hunter may spend refining the result; longer is more accurate. |
Returns
| Field | Type | Description |
|---|---|---|
| data.email | string | The best address found. |
| data.score | number | Confidence from 0 to 100. |
| data.verification | object | Verification status and date. |
| data.sources | array | Pages where the address was seen. |
Example call
curl "https://api.hunter.io/v2/email-verifier?email=patrick@stripe.com" -H "X-API-Key: $HUNTER_API_KEY" | jq .data.status
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| string | Required | The address to verify. |
Returns
| Field | Type | Description |
|---|---|---|
| data.status | string | valid, invalid, accept_all, webmail, disposable, unknown. |
| data.result | string | deliverable, undeliverable or risky. |
| data.score | number | Confidence from 0 to 100. |
| data.mx_records / smtp_server / smtp_check | boolean | The individual checks performed. |
Example call
const key = process.env.HUNTER_API_KEY;
const res = await fetch("https://api.hunter.io/v2/email-count?domain=stripe.com", { headers: { "X-API-Key": key } });
const { data } = await res.json();
console.log(data.total, data.personal_emails, data.generic_emails);Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| domain | string | Optional | Domain to count; required unless company is given. |
| company | string | Optional | Company name when you lack the domain. |
| type | string | Optional | Count only personal or generic addresses. |
Returns
| Field | Type | Description |
|---|---|---|
| data.total | number | Total addresses, with per-department and per-seniority counts alongside. |
Example call
import os, requests
KEY = os.getenv("HUNTER_API_KEY")
hits = requests.get("https://api.hunter.io/v2/domains-suggestion", params={"query": "grab", "limit": 5}, headers={"X-API-Key": KEY}).json()["data"]Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| query | string | Required | Company name, 3 to 100 characters. |
| limit | numberdefault 5 | Optional | Suggestions to return, 1 to 10. |
Returns
| Field | Type | Description |
|---|---|---|
| data | array | Candidate domains with company names. |
Example call
curl -X POST "https://api.hunter.io/v2/discover" -H "Content-Type: application/json" -H "X-API-Key: $HUNTER_KEY" \
-d '{
"query": "fintech companies in Singapore",
"headcount": ["51-200", "201-500"],
"headquarters_location": {"include": [{"country": "SG"}]},
"job_openings": {"hiring": true}
}'Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| query | string | Optional | Natural-language description; required unless a filter is set. |
| organization | object | Optional | Lists of domain and/or name to select on. |
| similar_to | object | Optional | A domain or name to find look-alike companies for. |
| headquarters_location | object | Optional | include and exclude location lists. |
| industry | object | Optional | Industries to include and exclude (vendor's industries.json). |
| headcount | array | Optional | Size bands such as 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+. |
| company_type | object | Optional | educational, government, nonprofit, partnership, private, public and so on, include and exclude. |
| year_founded | object | Optional | Years or a range (Premium plans). |
| keywords | object | Optional | Keyword include and exclude lists. |
| technology | object | Optional | Technologies in use, include and exclude (Premium plans). |
| funding | object | Optional | Funding series such as pre_seed, seed, series_a (Premium plans). |
| job_openings | object | Optional | hiring true plus optional role filters. |
| limit | numberdefault 100 | Optional | Companies per page, up to 100 (changeable on Premium). |
| offset | numberdefault 0 | Optional | Companies to skip, up to 10,000 (Premium). |
Returns
| Field | Type | Description |
|---|---|---|
| data | array | Matching companies with domain, industry, headcount, location and more. |
| meta | object | Result count and paging. |
Example call
const people = await fetch("https://api.hunter.io/v2/discover/people?query=payments+companies+in+France&industry[include][]=Financial+Services", {
headers: { "X-API-Key": process.env.HUNTER_API_KEY },
}).then((r) => r.json());Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| query | string | Optional | Plain-language description of the companies; a filter may replace it. |
| filters | object | Optional | Any Discover filter (industry, headcount, headquarters_location, technology, funding and the rest). |
| limit | numberdefault 100 | Optional | Page size, max 100; adjustable on Premium. |
| offset | numberdefault 0 | Optional | Rows to skip, max 10,000; Premium only. |
Returns
| Field | Type | Description |
|---|---|---|
| data | array | People with company, position and address fields. |
Example call
curl --header 'X-API-Key: YOUR_HUNTER_API_KEY' 'https://api.hunter.io/v2/people/find?email=matt@hunter.io'
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| string | Optional | The address to enrich; required unless linkedin_handle is given. | |
| linkedin_handle | string | Optional | LinkedIn handle alternative. |
| clearbit_format | booleandefault false | Optional | Clearbit-compatible output shape. |
Returns
| Field | Type | Description |
|---|---|---|
| data | object | Person record: name, employment, location, linkedin, twitter and the company's domain. |
Example call
http GET https://api.hunter.io/v2/companies/find domain==hunter.io X-API-Key:$HUNTER_API_KEY
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| domain | string | Required | The company domain. |
| clearbit_format | booleandefault false | Optional | Emit the Clearbit schema instead of Hunter's. |
Returns
| Field | Type | Description |
|---|---|---|
| data | object | Company record. |
Example call
import os, requests
auth = {"X-API-Key": os.environ.get("HUNTER_API_KEY")}
res = requests.get("https://api.hunter.io/v2/combined/find", params={"email": "matt@hunter.io"}, headers=auth)
person, company = res.json()["data"]["person"], res.json()["data"]["company"]Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| string | Required | The address to enrich. | |
| clearbit_format | booleandefault false | Optional | Return the Clearbit-compatible schema. |
Returns
| Field | Type | Description |
|---|---|---|
| data.person | object | Person record. |
| data.company | object | Company record. |
Example call
curl -X POST "https://api.hunter.io/v2/leads" --header "X-API-Key: $HUNTER_API_KEY" --header "Content-Type: application/json" \
-d '{"email": "jane@example.com", "first_name": "Jane", "last_name": "Tan", "position": "Head of Growth", "company": "Example", "website": "example.com", "country_code": "SG", "leads_list_name": "Fintech SG Q4", "source": "agent research"}'Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| string | Required | The lead's address. | |
| first_name | string | Optional | Given name. |
| last_name | string | Optional | Family name. |
| position | string | Optional | Job title. |
| company | string | Optional | Employer name. |
| company_industry | string | Optional | Sector, ideally from Hunter's recommended list. |
| company_size | string | Optional | Employer size band. |
| confidence_score | number | Optional | 0 to 100, usually the finder's score. |
| website | string | Optional | Employer domain. |
| country_code | string | Optional | ISO 3166-1 alpha-2. |
| department | string | Optional | Department. |
| linkedin_url | string | Optional | Public LinkedIn profile. |
| phone_number | string | Optional | Phone. |
| string | Optional | Twitter handle. | |
| notes | string | Optional | Free-text notes. |
| source | string | Optional | Where the lead came from. |
| leads_list_id | number | Optional | Target list; the last created list is used when omitted. |
| leads_list_ids | array | Optional | Several target lists. |
| leads_list_name | string | Optional | Target list by name, created if missing (255 characters max). |
| custom_attributes[slug] | string | Optional | Values for your team's custom attributes; an unknown slug returns 422. |
Returns
| Field | Type | Description |
|---|---|---|
| data.id | number | The new lead's id. |
Example call
curl -s https://api.hunter.io/v2/account --header "X-API-Key: $HUNTER_API_KEY" | jq .data.requests
Returns
| Field | Type | Description |
|---|---|---|
| data.requests | object | Searches and verifications used and available this period. |
| data.plan_name | string | Current plan. |
Hunter is an email-finding and verification service that agents reach through a hosted Model Context Protocol server at mcp.hunter.io, included on all plans, or through its REST API at api.hunter.io/v2. The tools cover Domain Search, Email Finder, Email Verifier, Discover (company search), person and company enrichment, and leads, with every address returned alongside a verification status and confidence score.
Hosted MCP on every plan
mcp.hunter.io works with Claude, ChatGPT, Gemini, Cursor and any MCP client, by OAuth or an X-API-Key header, at no extra cost.
Verified, not guessed
Every address returns a status and a confidence score, and the tools report when no verified contact exists instead of inventing one.
Domain Search with buyer filters
Seniority, department, decision-maker, job-title, location and verification-status filters narrow a company to the people worth contacting.
Discover at no credit cost
Natural-language company search with industry, headcount, headquarters, technology, funding and hiring filters.
Enrichment in Clearbit shape
Person, company and combined enrichment can return the Clearbit-compatible schema for drop-in replacement.
Leads to sequences
Agents can save contacts to named lists and, with a connected mailbox, hand them to outreach sequences and a CRM push.
Published agent setup files
agents.md, claude.md and gemini.md give assistants exact per-client instructions and a test key for a dry run.
Pre-call account research
Resolve the company's domain, run Domain Search filtered to executive seniority and the relevant department, and hand the agent names, titles and verified addresses in one turn.
Inbound lead qualification
Verify the sender's address, enrich the person and company from the email, and list colleagues in the buying department before the first reply.
CSV enrichment
For each row of first name, last name and company, call Email Finder with max_duration raised for accuracy, then Email Verifier, and return the original columns plus address, status and score.
Segment building with Discover
Query companies by industry, headcount and headquarters location at no credit cost, then spend credits only on the contacts worth reaching, saving them to a named leads list.
| Skill | Works with | Connects by | Checked |
|---|---|---|---|
| Claude · ChatGPT · Codex · Cursor +3 | MCP | 11 Oct | |
| Claude · Codex · Cursor · Windsurf +1 | MCP | 19 Aug | |
| Claude · ChatGPT · Codex · Cursor +1 | MCP | 11 Oct | |
| Claude · Cursor | MCP | 18 Oct |
Free gives 50 credits a month, one connected mailbox and the MCP server. Starter is $49 a month for 2,000 credits, Growth $149 for 10,000 and Scale $299 for 25,000, each about 30% cheaper billed yearly. Searches cost 1 credit each and verifications 0.5, Discover is free, and the API-only Data Platform sells 1,000 search credits for $50 and 1,000 verification credits for $11, valid 12 months.
In Claude Code, add the hunter-io marketplace and install the hunter plugin; it authorises by OAuth on the first tool call and the tools appear after a restart. The Claude Desktop, ChatGPT and Gemini apps connect the same way as a custom connector pointing at mcp.hunter.io. Cursor, VS Code, Windsurf and Codex send the key in an X-API-Key header from a user-level config, and a published test key lets you smoke-test the REST side before you have an account.
The vendor names Claude, ChatGPT, Gemini (app, CLI, AI Studio, Vertex), Cursor and its Grok Bot, VS Code Copilot, Windsurf and Codex, plus any MCP client through the mcp-remote bridge. Anything else can call the REST API directly, and the Google Sheets add-on and Chrome extension cover the non-agent routes.
If you only need an occasional lead pull and already run on the Orthogonal gateway, its Find Leads skill bills per call without a plan. If the job is filling many columns about companies or people with sources, Riveter's enrichment runs do that. For moving the results into a CRM, the Pipedrive MCP server is the complementary piece rather than an alternative.
They overlap on finding contacts but differ in depth and billing. Orthogonal Find Leads is a gateway tool paid per call from an Orthogonal balance, handy when prospecting is a small part of a larger agent. Hunter is the data owner: it adds verification scores, Discover for company segments, enrichment, leads lists and sequences, and it runs on a plan whose credits the whole team shares. Agents that prospect daily end up on Hunter; agents that prospect occasionally stay on the gateway.
Hunter is the email-finding service that sales teams have used for years through its web app, browser extension and Google Sheets add-on; this record covers the part that agents plug into. Since the launch of the hosted Hunter MCP server, any assistant that speaks the Model Context Protocol can search a company domain for people and addresses, find one person's email from a name and company, verify deliverability with a confidence score, discover companies by industry, size and location, enrich a contact or an account, and save the results as leads, all without leaving the chat. The vendor's pitch is grounding: when Hunter cannot verify a contact the tool says so rather than letting the model invent an address, and the MCP page cites data on more than 100 million companies.
The server lives at mcp.hunter.io over Streamable HTTP and is included in every plan, the free one too. Claude Code installs it as a plugin that bundles skills and the server and authorises by OAuth on first use; Claude Desktop, the ChatGPT app and the Gemini app connect the same way with no key in any file. Cursor, VS Code, Windsurf, Codex and any other client send an API key in an X-API-Key header, and clients that only run local servers bridge through mcp-remote. Underneath sits the REST API at api.hunter.io/v2, where every capability is a GET or POST with the key in the same header (a query-string key is accepted but discouraged). A published test key exercises the REST plumbing without an account; it is refused by the MCP endpoint.
Typical agent flows: research an account before a call by resolving the company's domain, pulling its contacts and ranking them by seniority and department; qualify an inbound lead by verifying the address and listing colleagues; enrich a CSV of names with verified addresses; or build a segment with Discover's natural-language query and headcount, industry and location filters, which costs no credits. The lead endpoints then push results into lists and, with a connected mailbox, into outreach sequences. On Hokai the closest neighbours are Orthogonal Find Leads, a pay-per-call lead finder on the Orthogonal gateway, Riveter, which enriches whole tables with sourced cells, and Pipedrive MCP Server for the CRM side of the same workflow; the Google Sheets skill is where many teams keep the lists Hunter fills.
Billing is credit-based: a search costs one credit and a verification half a credit, and a repeated lookup of the same address or domain is counted once per calendar month. Plans differ in monthly credits, connected email accounts for sequences, and saved-lead capacity; yearly billing takes roughly thirty percent off and grants the whole year's credits up front. An API-only Data Platform sells search and verification credits in packs that stay valid for twelve months, priced separately from the outreach plans.
Hunter publishes an agents.md and per-client setup files (claude.md, gemini.md) and keeps a prompt library for the MCP, which suggests the agent channel is now a first-class product rather than an add-on. If you are weighing an email finder against an enrichment platform or a lead database for your stack, Smart Match asks the questions that decide it.
Protocol, authentication, permissions and the call contracts on this page are read from Hunter's own documentation. The verdict is Hokai's reading of them, not the maintainer's claim.