Hunter MCP

io.scalablyPublished by scalably.iov1.0.0Updated Oct 24, 2026

Hunter.io MCP: domain search, email finder and verifier, enrichment, discovery, leads. 11 tools.

The publisher's own server: Hunter Lease

Overview

AI-generated overview

Wraps the Hunter.io API so an assistant can search domains, find and verify professional emails, enrich people and companies, and manage leads.

What you can do
Provides 11 tools over the Hunter.io v2 API: account_info for plan and credit usage, domain_search for emails at a company, email_finder and email_verifier, email_count, and person, company and combined enrichment (optionally Clearbit-compatible). Discover finds companies from natural-language or structured filters, and list_leads reads the leads list. Every tool returns plain JSON with status, summary, result, proof and warnings.
When to use it
Useful when an assistant needs professional contact data: finding or verifying an email for outreach, enriching a person or company record, prospecting companies by industry, size or technology, or reviewing existing Hunter leads.
Requirements
Runs locally over stdio, typically via npx @scalably-io/hunter-mcp or the .mcpb desktop bundle. Requires a Hunter.io account and the HUNTER_API_KEY secret; optional HUNTER_API_BASE, HUNTER_TIMEOUT_MS and HUNTER_RETRY_BASE_MS tune the endpoint, timeout and retry backoff. Network access to the Hunter API is needed, and usage consumes plan credits.
Before you install
The API key is a billable credential: searches, verification and enrichment consume Hunter plan credits, and quotas are visible through account_info. create_lead writes to your Hunter leads list and is the only non-read tool; the other 10 are read-only. Queries send domains, email addresses and LinkedIn handles to Hunter.io.

Installation

In SourceWeft

  1. Open Hunter MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Hunter MCP

Hunter.io MCP server. 11 tools cover domain search, email finding and verification, enrichment, company discovery, and lead management.

Install

Claude Code:

bash
claude mcp add hunter -e HUNTER_API_KEY=your-key -- npx -y @scalably-io/hunter-mcp

Codex:

bash
codex mcp add hunter --env HUNTER_API_KEY=your-key -- npx -y @scalably-io/hunter-mcp

Claude Desktop: download hunter-mcp.mcpb from the latest GitHub release and open it.

Setup

  1. Create an API key at hunter.io/api-keys.
  2. create_lead writes to your Hunter leads list and is the only non-read tool; the other 10 tools are read-only.

Tools (11)

ToolWhat it does
account_infoRead the Hunter v2 account plan and exact current credit usage, including remaining unified or per-type balances
domain_searchSearch Hunter v2 emails for one domain/company with current people, verification, location, job-title, decision-maker, aggregation, and offset filters
email_finderFind and automatically verify the most likely professional email from a company/domain plus name, or directly from a LinkedIn handle
email_verifierVerify one email address with Hunter v2 and return exact deliverability, score, SMTP/MX, accept-all, webmail, disposable, and source evidence
email_countCount Hunter email coverage for a domain/company, optionally limited to personal or generic addresses, without returning addresses
email_enrichmentEnrich a person from an email address or LinkedIn handle using Hunter v2, optionally in Clearbit-compatible format
company_enrichmentEnrich a company from its domain using Hunter v2, optionally in Clearbit-compatible format
combined_enrichmentEnrich both a person and their company from one email using Hunter v2, optionally in Clearbit-compatible format
discoverUse Hunter Discover v2 to find companies from current natural-language or structured organization, location, industry, headcount, type, year, keyword, technology, and funding filters
create_leadCreate one Hunter lead from a required email and optional current lead fields, list placement, and custom attributes. This is a single-attempt mutation
list_leadsList Hunter leads with current list, identity, company, status, verification, activity/date, location, tag, campaign, user, confidence, custom-attribute, query, and offset filters

Configuration

VariableRequiredPurpose
HUNTER_API_KEYyesHunter.io API key from hunter.io/api-keys
HUNTER_API_BASEnoOverride the Hunter API base URL (default https://api.hunter.io/v2)
HUNTER_TIMEOUT_MSnoPer-request timeout in milliseconds (default 30000)
HUNTER_RETRY_BASE_MSnoBase delay in milliseconds for the GET retry backoff (default 500)

Reply shape

Every tool returns plain JSON with status (succeeded, partial, no_op), operation, summary, target, result, proof, warnings, recovery. Failures throw a plain error string: <code>: <message> <hint>.

Limits

Hunter's per-plan request quotas surface in account_info.

Verify

Each release lists the package version, the .mcpb sha256 and the production commit it was derived from in CHANGELOG.md. CI runs the tests and a clean install of the packed tarball on every push.

Privacy Policy

This server runs locally, on your machine, under your own credentials. It collects no personal data, contains no telemetry, stores nothing persistently, and talks only to the vendor API it wraps. No third party, including Scalably, receives your data. Contact: [email protected]. Canonical copy: https://scalably.io/connector-privacy.html

License

MIT. Copyright Scalably.

Source: README.md at commit b4feffb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Hunter integrations