Hunter review, pricing and limits

Find, verify and enrich professional email addresses from inside an agent, over MCP or REST.

Best for
SDRs and founders prospecting inside an assistant
Not for
Teams that need deep firmographic enrichment beyond contact data
  • Data
  • Web search
  • App connectors

Should you use Hunter?

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.

Also for

  • Developers building sales agents
  • SDRs and founders prospecting from inside Claude, ChatGPT or Gemini
Show 3 more
  • Developers wiring verified email data into sales agents and CRMs
  • RevOps teams replacing CSV exports with agent-driven list building
  • Teams migrating from Clearbit-shaped enrichment

Main trade-off

Unpublished rate limits and Premium-only Discover paging and filters.

Hunter pricing

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.

Billing model
Freemium

Install Hunter

claude plugin marketplace add hunter-io/claude-plugin && claude plugin install hunter@hunter

Before you start

  • A Hunter account; the free plan is enough to run every tool and the MCP server is included on all plans
  • For header clients: an API key from hunter.io/api-keys placed in the client's user-level MCP config as X-API-Key, never in a committed project file
  • For OAuth clients (Claude Code plugin, Claude Desktop, ChatGPT, Gemini): sign in when the first tool call prompts; tools appear after a restart in Claude Code
  • A connected mailbox only if the agent should start outreach sequences

How to invoke it

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.

Works with

  • Claude Code (plugin: hunter-io/claude-plugin)
  • Claude Desktop and claude.ai (OAuth connector)
  • ChatGPT app
  • Gemini app, Gemini CLI, AI Studio, Vertex
  • Cursor and Grok Bot (plugin marketplace)
  • VS Code Copilot, Windsurf, Codex
  • Any MCP client via mcp-remote

Required runtime

  • Any MCP client (Claude Code plugin, Claude Desktop, ChatGPT, Gemini, Cursor, VS Code, Windsurf, Codex)
  • Node 18 or newer only for the mcp-remote bridge
  • Any HTTP client for the REST API; a Google Sheets add-on and a Chrome extension exist for non-agent use

Where it runs

  • Web
  • API

Data it can reach

  • professional email addresses and the people behind a domain
  • deliverability status and confidence scores
  • company records (industry, headcount, location, technology, funding) via Discover and enrichment
  • your own Hunter leads, lists and sequences

The permissions this connector asks for, as its own documentation states them.

What Hunter can do

12 actions an agent can call. Open one for its parameters and an example.

Domain SearchLists the people and email addresses Hunter has for a company domain, with filters for seniority, department, decision makers, location, job titles and verification status.

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

ParameterTypeNeededDescription
domainstringOptionalCompany domain, e.g. stripe.com; required unless company is given and preferred over it.
companystringOptionalCompany name when the domain is unknown.
limitnumberdefault 10OptionalMaximum addresses to return.
offsetnumberdefault 0OptionalAddresses to skip for paging.
typestringOptionalpersonal or generic.
senioritystringOptionaljunior, senior or executive, comma-separated.
departmentstringOptionalOne or more of executive, it, finance, management, sales, legal, support, hr, marketing, communication, education, design, health, operations, product, research, consulting, administrative, procurement.
decision_makerbooleanOptionalOnly buying-authority contacts (true) or only the rest (false).
required_fieldstringOptionalfull_name, position and/or phone_number must be present.
verification_statusstringOptionalvalid, accept_all and/or unknown.
locationobjectOptionalinclude and exclude lists of continent, business_region, country, state or city (POST only).
job_titlesstringOptionalComma-separated job titles to match.
aggregationsbooleandefault falseOptionalAdd a per-department and per-seniority breakdown in meta.aggregations.

Returns

FieldTypeDescription
data.emailsarrayvalue, type, confidence, first_name, last_name, position, seniority, department, sources and verification for each address.
data.patternstringThe domain's most common address pattern, e.g. {first}.
meta.resultsnumberTotal addresses available for paging.
Email FinderReturns the most likely email address for a named person at a company, with a confidence score and the sources it was seen on.

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

ParameterTypeNeededDescription
domainstringOptionalCompany domain; required unless company or linkedin_handle is given.
companystringOptionalEmployer name if the domain is unknown.
linkedin_handlestringOptionalLinkedIn profile handle as an alternative to name plus company.
first_namestringOptionalGiven name; required with last_name unless full_name or linkedin_handle is used.
last_namestringOptionalFamily name.
full_namestringOptionalFull name when first and last are not separable.
max_durationnumberOptionalSeconds Hunter may spend refining the result; longer is more accurate.

Returns

FieldTypeDescription
data.emailstringThe best address found.
data.scorenumberConfidence from 0 to 100.
data.verificationobjectVerification status and date.
data.sourcesarrayPages where the address was seen.
Email VerifierChecks whether an email address is deliverable and returns a status, a score and the checks behind them.

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

ParameterTypeNeededDescription
emailstringRequiredThe address to verify.

Returns

FieldTypeDescription
data.statusstringvalid, invalid, accept_all, webmail, disposable, unknown.
data.resultstringdeliverable, undeliverable or risky.
data.scorenumberConfidence from 0 to 100.
data.mx_records / smtp_server / smtp_checkbooleanThe individual checks performed.
Email CountReturns how many addresses Hunter holds for a domain or company, free of charge, split by type, department and seniority.

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

ParameterTypeNeededDescription
domainstringOptionalDomain to count; required unless company is given.
companystringOptionalCompany name when you lack the domain.
typestringOptionalCount only personal or generic addresses.

Returns

FieldTypeDescription
data.totalnumberTotal addresses, with per-department and per-seniority counts alongside.
Domains SuggestionSuggests the web domains that match a company name, for resolving a name before a Domain Search.

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

ParameterTypeNeededDescription
querystringRequiredCompany name, 3 to 100 characters.
limitnumberdefault 5OptionalSuggestions to return, 1 to 10.

Returns

FieldTypeDescription
dataarrayCandidate domains with company names.
Discover CompaniesFinds companies from a natural-language query and structured filters (industry, headcount, headquarters, type, keywords, hiring); costs no credits.

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

ParameterTypeNeededDescription
querystringOptionalNatural-language description; required unless a filter is set.
organizationobjectOptionalLists of domain and/or name to select on.
similar_toobjectOptionalA domain or name to find look-alike companies for.
headquarters_locationobjectOptionalinclude and exclude location lists.
industryobjectOptionalIndustries to include and exclude (vendor's industries.json).
headcountarrayOptionalSize bands such as 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+.
company_typeobjectOptionaleducational, government, nonprofit, partnership, private, public and so on, include and exclude.
year_foundedobjectOptionalYears or a range (Premium plans).
keywordsobjectOptionalKeyword include and exclude lists.
technologyobjectOptionalTechnologies in use, include and exclude (Premium plans).
fundingobjectOptionalFunding series such as pre_seed, seed, series_a (Premium plans).
job_openingsobjectOptionalhiring true plus optional role filters.
limitnumberdefault 100OptionalCompanies per page, up to 100 (changeable on Premium).
offsetnumberdefault 0OptionalCompanies to skip, up to 10,000 (Premium).

Returns

FieldTypeDescription
dataarrayMatching companies with domain, industry, headcount, location and more.
metaobjectResult count and paging.
Discover PeopleFinds people at the companies a Discover query matches, accepting every Discover filter.

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

ParameterTypeNeededDescription
querystringOptionalPlain-language description of the companies; a filter may replace it.
filtersobjectOptionalAny Discover filter (industry, headcount, headquarters_location, technology, funding and the rest).
limitnumberdefault 100OptionalPage size, max 100; adjustable on Premium.
offsetnumberdefault 0OptionalRows to skip, max 10,000; Premium only.

Returns

FieldTypeDescription
dataarrayPeople with company, position and address fields.
Email EnrichmentReturns what Hunter knows about a person from an email address or LinkedIn handle: name, position, company, location and social profiles.

Example call

curl --header 'X-API-Key: YOUR_HUNTER_API_KEY' 'https://api.hunter.io/v2/people/find?email=matt@hunter.io'

Parameters

ParameterTypeNeededDescription
emailstringOptionalThe address to enrich; required unless linkedin_handle is given.
linkedin_handlestringOptionalLinkedIn handle alternative.
clearbit_formatbooleandefault falseOptionalClearbit-compatible output shape.

Returns

FieldTypeDescription
dataobjectPerson record: name, employment, location, linkedin, twitter and the company's domain.
Show all 12 actions
Company EnrichmentReturns a company profile for a domain: name, description, industry, size, location, technologies and social handles.

Example call

http GET https://api.hunter.io/v2/companies/find domain==hunter.io X-API-Key:$HUNTER_API_KEY

Parameters

ParameterTypeNeededDescription
domainstringRequiredThe company domain.
clearbit_formatbooleandefault falseOptionalEmit the Clearbit schema instead of Hunter's.

Returns

FieldTypeDescription
dataobjectCompany record.
Combined EnrichmentReturns the person and their company in one call from an email address.

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

ParameterTypeNeededDescription
emailstringRequiredThe address to enrich.
clearbit_formatbooleandefault falseOptionalReturn the Clearbit-compatible schema.

Returns

FieldTypeDescription
data.personobjectPerson record.
data.companyobjectCompany record.
Create LeadSaves a contact into a Hunter leads list, with company, position, score, country, LinkedIn, phone, notes and custom attributes.

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

ParameterTypeNeededDescription
emailstringRequiredThe lead's address.
first_namestringOptionalGiven name.
last_namestringOptionalFamily name.
positionstringOptionalJob title.
companystringOptionalEmployer name.
company_industrystringOptionalSector, ideally from Hunter's recommended list.
company_sizestringOptionalEmployer size band.
confidence_scorenumberOptional0 to 100, usually the finder's score.
websitestringOptionalEmployer domain.
country_codestringOptionalISO 3166-1 alpha-2.
departmentstringOptionalDepartment.
linkedin_urlstringOptionalPublic LinkedIn profile.
phone_numberstringOptionalPhone.
twitterstringOptionalTwitter handle.
notesstringOptionalFree-text notes.
sourcestringOptionalWhere the lead came from.
leads_list_idnumberOptionalTarget list; the last created list is used when omitted.
leads_list_idsarrayOptionalSeveral target lists.
leads_list_namestringOptionalTarget list by name, created if missing (255 characters max).
custom_attributes[slug]stringOptionalValues for your team's custom attributes; an unknown slug returns 422.

Returns

FieldTypeDescription
data.idnumberThe new lead's id.
AccountReturns the account behind the key: plan, credits used and remaining, reset date and team.

Example call

curl -s https://api.hunter.io/v2/account --header "X-API-Key: $HUNTER_API_KEY" | jq .data.requests

Returns

FieldTypeDescription
data.requestsobjectSearches and verifications used and available this period.
data.plan_namestringCurrent plan.

What Hunter is for

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.

Show all 7 features
  • 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.

What people use it for

  • 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.

Strengths and limits

Strengths

  • The free plan runs every tool and the MCP server, so an agent integration can be proven before any spend.
  • Repeated lookups of the same address in a calendar month are not charged again, which suits agents that re-check.
  • OAuth paths for Claude, ChatGPT and Gemini keep the API key out of config files entirely.

Limits

  • Per-minute rate limits are not published on the API pages read; agents learn them from 429 responses.
  • Changing Discover's page size or offset, and the technology, funding and founding-year filters, are reserved for Premium plans.
  • Monthly credits expire without rolling over, so bursty prospecting fits the yearly or Data Platform options better.

Hunter alternatives

SkillWorks withConnects byChecked
Hunter This pageClaude · ChatGPT · Codex · Cursor +3MCP11 Oct
Orthogonal Find LeadsPick Orthogonal Find Leads for occasional pay-per-call lead pulls inside that gateway; pick Hunter when you want verification scores, Discover and leads lists on a plan you already hold.Claude · Codex · Cursor · Windsurf +1MCP19 Aug
RiveterPick Riveter to enrich whole tables with sourced cells across any attribute; pick Hunter when the attribute you need is a verified email address.Claude · ChatGPT · Codex · Cursor +1MCP11 Oct
MireyeCited physical-world data for AI agents at any US location.Claude · CursorMCP18 Oct

Hunter facts

Protocol
MCP
Authentication
API key
Latency class
Fast
Open source
No
Rate limits
Per-minute limits are not stated on the pages read; the API returns 429 when rate-limited (agents.md). Credits: a search costs 1 credit and a verification 0.5; a repeated search or verification of the same target is counted once per calendar month; Discover is free. Domain Search returns 10 results by default with limit and offset for paging; Discover returns up to 100 per page, with limit and offset changes reserved for Premium plans (hunter.io/api-documentation/v2, read 11 October 2026).

Questions about Hunter

What do Hunter credits cost and what does the free plan allow?

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.

How does an agent connect to Hunter without pasting keys into files?

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.

Which assistants and clients does Hunter support?

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.

When would a different lead or enrichment skill fit better?

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.

Hunter or Orthogonal Find Leads for an agent that prospects?

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.

About Hunter

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.

Read the full background

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.

Sources and guides

More Agent Skills on Hokai

  • Manifold MCPRead-only marketing data tools for your AI agent over one MCP link
  • Logo.devAny company's logo, brandmark, colours and socials for an agent, by domain, ticker or name, over MCP or REST.
  • TombaEmail finding, verification, phone and company data for agents over a remote MCP server with OAuth.