Hby Hunter
Verify an email address
Checks whether an email address is deliverable and returns its status (valid, invalid, accept_all, webmail, disposable or unknown), a score and the checks behind it.
Description
Pass the `email`. A verification that runs past 20 seconds returns `202`: call again with the same email until the result arrives, which still counts as one request. Read `status`; the older `result` field is deprecated. A verification costs half a credit, and a verified email is also saved to your Hunter leads unless that is turned off for the account.
verify-email.md
Verify an email address
Checks whether an email address is deliverable and returns its status (valid, invalid, accept_all, webmail, disposable or unknown), a score and the checks behind it.
Pass the email. A verification that runs past 20 seconds returns 202:
call again with the same email until the result arrives, which still counts
as one request. Read status; the older result field is deprecated. A
verification costs half a credit, and a verified email is also saved to your
Hunter leads unless that is turned off for the account.
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-Verifier.
Server URL: https://mcp.hunter.io/mcp
API (official)
- Base URL: https://api.hunter.io/v2
- Endpoint:
GET /email-verifier - 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.