Skip to main content
Glama
Hunter.io MCP Server

Hunter.io MCP Server

by Meerkats-Ai

Hunter.io MCP Server

This is a Model Context Protocol (MCP) server that integrates with the Hunter.io API to provide email finding and verification capabilities.

Features

  • Find email addresses using domain and name information

  • Verify email addresses for deliverability and validity

Related MCP server: Hunter MCP Server

Setup

Local Setup

  1. Clone this repository

  2. Install dependencies:

    npm install
  3. Create a .env file based on .env.example and add your Hunter.io API key:

    HUNTER_API_KEY=your_api_key_here
  4. Build the server:

    npm run build
  5. Start the server:

    npm start

Docker Setup

  1. Clone this repository

  2. Create a .env file with your Hunter.io API key

  3. Build and run using Docker Compose:

    docker-compose up -d

MCP Configuration

To use this server with an MCP client, add the following configuration to your MCP settings file:

{
  "mcpServers": {
    "hunter.io": {
      "command": "node",
      "args": ["path/to/hunter.io/dist/index.js"],
      "env": {
        "HUNTER_API_KEY": "your_api_key_here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Available Tools

  • hunter_find_email: Find an email address using domain and name information

  • hunter_verify_email: Verify if an email address is valid and deliverable

License

ISC

Available Tools

5 tools
hunter_account_infoB

Get information regarding your Hunter account.

Inputs: no named parameters.

hunter_email_countB

Know how many email addresses we have for a domain or a company.

Inputs: company, domain.

hunter_find_emailC

Find an email address using domain and name information.

Inputs: domain (required), company, first_name, full_name, +1 more.

hunter_verify_emailB

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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: account info retrieval, domain-wide email discovery, email count estimation, targeted email lookup, and email verification. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent 'hunter_verb_noun' pattern with snake_case, using descriptive verbs like 'account_info', 'domain_search', 'email_count', 'find_email', and 'verify_email'. This uniformity enhances predictability and readability.

    Tool Count5/5

    With 5 tools, this server is well-scoped for email discovery and verification tasks. Each tool serves a unique and necessary function, covering core operations without bloat or redundancy, making the count ideal for the domain.

    Completeness4/5

    The toolset provides comprehensive coverage for email discovery and verification workflows, including search, count, targeted lookup, and validation. A minor gap might be the absence of tools for managing saved searches or batch operations, but core functionality is complete.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      F
      maintenance
      Provides 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.
      6
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Wraps the Hunter.io email finder and verification API, enabling email lookup and verification via MCP.
      134 npm
      MIT