Hunter MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUNTER_API_KEY | Yes | Hunter.io API key from hunter.io/api-keys | |
| HUNTER_API_BASE | No | Override the Hunter API base URL (default https://api.hunter.io/v2) | https://api.hunter.io/v2 |
| HUNTER_TIMEOUT_MS | No | Per-request timeout in milliseconds (default 30000) | 30000 |
| HUNTER_RETRY_BASE_MS | No | Base delay in milliseconds for the GET retry backoff (default 500) | 500 |
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_infoA | Read the Hunter v2 account plan and exact current credit usage, including remaining unified or per-type balances. |
| domain_searchB | Search Hunter v2 emails for one domain/company with current people, verification, location, job-title, decision-maker, aggregation, and offset filters. |
| email_finderB | Find and automatically verify the most likely professional email from a company/domain plus name, or directly from a LinkedIn handle. |
| email_verifierA | Verify one email address with Hunter v2 and return exact deliverability, score, SMTP/MX, accept-all, webmail, disposable, and source evidence. |
| email_countA | Count Hunter email coverage for a domain/company, optionally limited to personal or generic addresses, without returning addresses. |
| email_enrichmentA | Enrich a person from an email address or LinkedIn handle using Hunter v2, optionally in Clearbit-compatible format. |
| company_enrichmentA | Enrich a company from its domain using Hunter v2, optionally in Clearbit-compatible format. |
| combined_enrichmentA | Enrich both a person and their company from one email using Hunter v2, optionally in Clearbit-compatible format. |
| discoverB | Use Hunter Discover v2 to find companies from current natural-language or structured organization, location, industry, headcount, type, year, keyword, technology, and funding filters. |
| create_leadA | Create one Hunter lead from a required email and optional current lead fields, list placement, and custom attributes. This is a single-attempt mutation. |
| list_leadsB | List Hunter leads with current list, identity, company, status, verification, activity/date, location, tag, campaign, user, confidence, custom-attribute, query, and offset filters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/scalably-io/hunter-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server