hunter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUNTER_API_KEY | Yes | Your Hunter.io API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_email_by_nameB | Find the most likely email address for a person at a company domain |
| verify_emailA | Verify if an email address is valid and deliverable |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.