Skip to main content
Glama
Meerkats-Ai

Hunter.io MCP Server

by Meerkats-Ai

hunter_verify_email

Check email validity and deliverability using domain and name data to ensure accurate communication and reduced bounce rates.

Instructions

Verify if an email address is valid and deliverable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesThe email address to verify

Implementation Reference

  • Handler function for 'hunter_verify_email' tool: validates input using isVerifyEmailParams, calls Hunter.io /email-verifier API endpoint with retry logic via withRetry, returns formatted JSON response or error message.
    case 'hunter_verify_email': {
      if (!isVerifyEmailParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for hunter_verify_email'
        );
      }
    
      try {
        // Hunter.io API expects query parameters for email verification
        const response = await withRetry(
          async () => apiClient.get('/email-verifier', { params: args }),
          'verify email'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
          isError: false,
        };
      } catch (error) {
        const errorMessage = axios.isAxiosError(error)
          ? `API Error: ${error.response?.data?.message || error.message}`
          : `Error: ${error instanceof Error ? error.message : String(error)}`;
    
        return {
          content: [{ type: 'text', text: errorMessage }],
          isError: true,
        };
      }
    }
  • Tool definition including name, description, and input schema (requires 'email' string). This is used for both documentation and validation.
    const VERIFY_EMAIL_TOOL: Tool = {
      name: 'hunter_verify_email',
      description: 'Verify if an email address is valid and deliverable.',
      inputSchema: {
        type: 'object',
        properties: {
          email: {
            type: 'string',
            description: 'The email address to verify',
          }
        },
        required: ['email'],
      },
    };
  • src/index.ts:423-431 (registration)
    Registers the 'hunter_verify_email' tool (as VERIFY_EMAIL_TOOL) in the list of available tools returned by the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        FIND_EMAIL_TOOL,
        VERIFY_EMAIL_TOOL,
        DOMAIN_SEARCH_TOOL,
        EMAIL_COUNT_TOOL,
        ACCOUNT_INFO_TOOL,
      ],
    }));
  • Type guard helper function used in the handler to validate that input arguments match the expected VerifyEmailParams shape (object with 'email' string).
    function isVerifyEmailParams(args: unknown): args is VerifyEmailParams {
      return (
        typeof args === 'object' &&
        args !== null &&
        'email' in args &&
        typeof (args as { email: unknown }).email === 'string'
      );
    }
  • TypeScript interface defining the input parameters for the 'hunter_verify_email' tool.
    interface VerifyEmailParams {
      email: string;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'verify' implies a read-only check, the description doesn't mention rate limits, authentication requirements, what 'deliverable' means operationally, or what the verification process entails. It provides minimal behavioral context beyond the basic purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple verification tool and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter verification tool with no output schema, the description adequately covers the basic purpose. However, without annotations or output schema, it lacks details about the verification process, result format, or behavioral constraints that would be helpful for an AI agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the single parameter 'email' already documented in the schema. The description doesn't add any additional parameter semantics beyond what's in the schema (e.g., format requirements, examples, or edge cases). Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('verify') and resource ('email address'), and specifies the verification criteria ('valid and deliverable'). However, it doesn't differentiate this email verification tool from the sibling tools (like domain_search or find_email) which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the sibling tools (hunter_domain_search, hunter_find_email, etc.). It doesn't mention prerequisites, alternatives, or specific contexts where email verification is appropriate versus other email-related operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

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/Meerkats-Ai/hunter-io-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server