hunter-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hunter-mcp find email for John Smith at google.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hunter.io MCP Server
MCP server for Hunter.io email finder and verifier.
Setup
Get your API key from Hunter.io
Create the secrets file:
mkdir -p ~/.claude/secrets/hunter
echo "HUNTER_API_KEY=your_api_key_here" > ~/.claude/secrets/hunter/.envInstall dependencies:
pnpm installAdd to your Claude config (
~/.claude.json):
{
"mcpServers": {
"hunter": {
"command": "npx",
"args": ["tsx", "/Users/brenner/repos/hunter-mcp/src/index.ts"]
}
}
}Related MCP server: mcp-hunter
Tools
find_email_by_name
Find the most likely email address for a person at a company.
Parameters:
domain- Company domain (e.g., "stripe.com")first_name- Person's first namelast_name- Person's last name
Returns: { email, score, status }
verify_email
Verify if an email address is valid and deliverable.
Parameters:
email- Email address to verify
Returns: { email, status, score }
Status values: valid, invalid, accept_all, webmail, disposable, unknown
Available Tools
2 toolsfind_email_by_nameEmail FinderB
Find the most likely email address for a person at a company domain
Inputs: domain (required), last_name (required), first_name (required).
verify_emailEmail VerifierA
Verify if an email address is valid and deliverable
Inputs: email (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
Each tool has a clearly distinct purpose: one discovers an email address from a name and domain, the other checks if an existing email is deliverable. No overlap or confusion.
Both tools follow a consistent verb_noun pattern: find_email_by_name and verify_email. The naming is predictable and readable.
Only two tools, which is slightly below the typical 3-15 range, but they cover the core functions of an email lookup/verification service and each tool is essential.
The stated domain is email discovery and validation, and the two tools provide a complete workflow: find an email, then verify it. No obvious gaps for the intended use case.
Maintenance
Related MCP Connectors
Find and verify work emails by name, company, role or LinkedIn URL, and find who is behind an email.
Find B2B decision makers and verify work emails.
Find and verify work emails with live SMTP checks and catch-all detection. Free 10 calls/day.
Find verified B2B emails and phone numbers; search and enrich people and companies for prospecting.
Related MCP Servers
AlicenseBqualityFmaintenanceProvides integration between Hunter API and LLM providers supporting the MCP protocol, allowing natural language interaction with Hunter B2B data for finding and managing company and people information.68MIT- AlicenseNot gradedqualityCmaintenanceWraps the Hunter.io email finder and verification API, enabling email lookup and verification via MCP.510 npmMIT
- AlicenseAqualityDmaintenanceFinds and verifies business email addresses using DNS/SMTP verification and web scraping, with no external API costs.522 npm12MIT
- AlicenseBqualityBmaintenanceEnables users to search domains, find and verify email addresses, enrich people and companies, discover companies, and manage leads through the Hunter.io API.1165 npmMIT