Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hunter MCP

NPM · @SCALABLY-IO/HUNTER-MCP · 2 COMPONENTS · SCANNED SEP 20

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

+5 this week 70 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 71 of 191 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1233 tokens (~112/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 6% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Hunter MCP server?

Hunter MCP runs locally as an npm package, launched with npx -y @scalably-io/hunter-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @scalably-io/hunter-mcp

# add to Claude Code
claude mcp add io-scalably-hunter-mcp -- npx -y @scalably-io/hunter-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "io-scalably-hunter-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scalably-io/hunter-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-scalably-hunter-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scalably-io/hunter-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-scalably-hunter-mcp -- npx -y @scalably-io/hunter-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-scalably-hunter-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@scalably-io/hunter-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-scalably-hunter-mcp --command npx --arg -y --arg @scalably-io/hunter-mcp
# ~/.hermes/config.yaml
mcp_servers:
  io-scalably-hunter-mcp:
    command: "npx"
    args: ["-y", "@scalably-io/hunter-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-scalably-hunter-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@scalably-io/hunter-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-scalably-hunter-mcp -t stdio -c npx -a -y @scalably-io/hunter-mcp
// mcp.json
{
  "mcpServers": {
    "io-scalably-hunter-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scalably-io/hunter-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +3
    • Stability: unverified → 0.23 functional
  • 9 Sept 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@scalably-io/hunter-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 191 packages
Packages resolved 191
Deprecated 2
Stale 70
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,233 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_info ~29

Read the Hunter v2 account plan and exact current credit usage, including remaining unified or per-type balances.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

combined_enrichment ~58

Enrich both a person and their company from one email using Hunter v2, optionally in Clearbit-compatible format.

NameTypeReqDescription
clearbit_formatbooleanReturn Hunter enrichment data in Clearbit-compatible field shape.
emailstringyes

No output schema declared.

No examples provided.

company_enrichment ~54

Enrich a company from its domain using Hunter v2, optionally in Clearbit-compatible format.

NameTypeReqDescription
clearbit_formatbooleanReturn Hunter enrichment data in Clearbit-compatible field shape.
domainstringyes

No output schema declared.

No examples provided.

create_lead ~187

Create one Hunter lead from a required email and optional current lead fields, list placement, and custom attributes. This is a single-attempt mutation.

NameTypeReqDescription
companystring
company_industrystring
company_sizestring
confidence_scoreinteger
country_codestring
custom_attributesobject
emailstringyes
first_namestring
last_namestring
leads_list_idinteger
leads_list_idsarray
leads_list_namestring
linkedin_urlstring
notesstring
phone_numberstring
positionstring
sourcestring
twitterstring
websitestring

No output schema declared.

No examples provided.

discover ~139

Use Hunter Discover v2 to find companies from current natural-language or structured organization, location, industry, headcount, type, year, keyword, technology, and funding filters.

NameTypeReqDescription
company_typeobject
fundingobject
headcountarray
headquarters_locationobject
industryobject
keywordsobject
limitinteger
offsetinteger
organizationobject
querystring
similar_toobject
technologyobject
year_foundedobject

No output schema declared.

No examples provided.

domain_search ~135

Search Hunter v2 emails for one domain/company with current people, verification, location, job-title, decision-maker, aggregation, and offset filters.

NameTypeReqDescription
aggregationsboolean
companystring
decision_makerboolean
departmentarray
domainstring
job_titlesarray
limitinteger
locationobject
offsetinteger
required_fieldarray
seniorityarray
typestring
verification_statusarray

No output schema declared.

No examples provided.

email_count ~50

Count Hunter email coverage for a domain/company, optionally limited to personal or generic addresses, without returning addresses.

NameTypeReqDescription
companystring
domainstring
typestring

No output schema declared.

No examples provided.

email_enrichment ~67

Enrich a person from an email address or LinkedIn handle using Hunter v2, optionally in Clearbit-compatible format.

NameTypeReqDescription
clearbit_formatbooleanReturn Hunter enrichment data in Clearbit-compatible field shape.
emailstring
linkedin_handlestring

No output schema declared.

No examples provided.

email_finder ~87

Find and automatically verify the most likely professional email from a company/domain plus name, or directly from a LinkedIn handle.

NameTypeReqDescription
companystring
domainstring
first_namestring
full_namestring
last_namestring
linkedin_handlestring
max_durationinteger

No output schema declared.

No examples provided.

email_verifier ~48

Verify one email address with Hunter v2 and return exact deliverability, score, SMTP/MX, accept-all, webmail, disposable, and source evidence.

NameTypeReqDescription
emailstringyes

No output schema declared.

No examples provided.

list_leads ~379

List Hunter leads with current list, identity, company, status, verification, activity/date, location, tag, campaign, user, confidence, custom-attribute, query, and offset filters.

NameTypeReqDescription
campaign_idsarray
campaign_membershipstring
companystring
company_sizestring
confidence_scoreobject
country_codestring
created_rangeobject
custom_attributesobject
departmentsarray
emailstring
first_namestring
industrystring
last_activity_atstringHunter period preset, *, ~, or supported date value.
last_activity_rangeobject
last_contacted_atstringHunter period preset, *, ~, or supported date value.
last_contacted_rangeobject
last_exported_atstringHunter period preset, *, ~, or supported date value.
last_exported_rangeobject
last_namestring
leads_list_idinteger
limitinteger
linkedin_urlstring
locationobject
offsetinteger
phone_numberstring
positionsarray
querystring
sending_statusesarray
sourcestring
sync_statusstring
tag_idsarray
twitterstring
updated_rangeobject
user_idsarray
verification_date_rangeobject
verification_statusesarray
websitestring

No output schema declared.

No examples provided.

Common questions

What is the Hunter MCP server?

Hunter MCP is listed in the public MCP registry as io.scalably/hunter-mcp. Hunter.io MCP: domain search, email finder and verifier, enrichment, discovery, leads. 11 tools. This page covers its npm package (@scalably-io/hunter-mcp).

Is the Hunter MCP server safe to use?

Hunter MCP scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Hunter MCP server expose?

Hunter MCP exposes 11 tools: account_info, domain_search, email_finder, email_verifier, email_count, and 6 more. Their descriptions and schemas cost roughly 1,233 tokens of context every time the server is loaded.

Is the Hunter MCP server still maintained?

Hunter MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Hunter MCP server under?

Hunter MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.