Hunter MCP
NPM · @SCALABLY-IO/HUNTER-MCP · 2 COMPONENTS
Hunter.io MCP: domain search, email finder and verifier, enrichment, discovery, leads. 11 tools.
Available components
Last scanned (5 hours ago)
Scores higher than 37% of npm servers
Category CRM and Sales
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 4.5.4, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 70 of 189 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management67
- Stability observed for 20 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
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.
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 16 Oct 26 +41
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 9 Oct 26 −39
- Tool safety: pass → unverified ▼ security
- Stability: 0.83 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 189 packages
| Packages resolved | 189 |
|---|---|
| Deprecated | 1 |
| Stale | 69 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clearbit_format | boolean | – | Return Hunter enrichment data in Clearbit-compatible field shape. |
| string | yes | – |
No output schema declared.
No examples provided.
company_enrichment ~54
Enrich a company from its domain using Hunter v2, optionally in Clearbit-compatible format.
| Name | Type | Req | Description |
|---|---|---|---|
| clearbit_format | boolean | – | Return Hunter enrichment data in Clearbit-compatible field shape. |
| domain | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| company_industry | string | – | – |
| company_size | string | – | – |
| confidence_score | integer | – | – |
| country_code | string | – | – |
| custom_attributes | object | – | – |
| string | yes | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| leads_list_id | integer | – | – |
| leads_list_ids | array | – | – |
| leads_list_name | string | – | – |
| linkedin_url | string | – | – |
| notes | string | – | – |
| phone_number | string | – | – |
| position | string | – | – |
| source | string | – | – |
| string | – | – | |
| website | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_type | object | – | – |
| funding | object | – | – |
| headcount | array | – | – |
| headquarters_location | object | – | – |
| industry | object | – | – |
| keywords | object | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| organization | object | – | – |
| query | string | – | – |
| similar_to | object | – | – |
| technology | object | – | – |
| year_founded | object | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregations | boolean | – | – |
| company | string | – | – |
| decision_maker | boolean | – | – |
| department | array | – | – |
| domain | string | – | – |
| job_titles | array | – | – |
| limit | integer | – | – |
| location | object | – | – |
| offset | integer | – | – |
| required_field | array | – | – |
| seniority | array | – | – |
| type | string | – | – |
| verification_status | array | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| domain | string | – | – |
| type | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clearbit_format | boolean | – | Return Hunter enrichment data in Clearbit-compatible field shape. |
| string | – | – | |
| linkedin_handle | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| domain | string | – | – |
| first_name | string | – | – |
| full_name | string | – | – |
| last_name | string | – | – |
| linkedin_handle | string | – | – |
| max_duration | integer | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_ids | array | – | – |
| campaign_membership | string | – | – |
| company | string | – | – |
| company_size | string | – | – |
| confidence_score | object | – | – |
| country_code | string | – | – |
| created_range | object | – | – |
| custom_attributes | object | – | – |
| departments | array | – | – |
| string | – | – | |
| first_name | string | – | – |
| industry | string | – | – |
| last_activity_at | string | – | Hunter period preset, *, ~, or supported date value. |
| last_activity_range | object | – | – |
| last_contacted_at | string | – | Hunter period preset, *, ~, or supported date value. |
| last_contacted_range | object | – | – |
| last_exported_at | string | – | Hunter period preset, *, ~, or supported date value. |
| last_exported_range | object | – | – |
| last_name | string | – | – |
| leads_list_id | integer | – | – |
| limit | integer | – | – |
| linkedin_url | string | – | – |
| location | object | – | – |
| offset | integer | – | – |
| phone_number | string | – | – |
| positions | array | – | – |
| query | string | – | – |
| sending_statuses | array | – | – |
| source | string | – | – |
| sync_status | string | – | – |
| tag_ids | array | – | – |
| string | – | – | |
| updated_range | object | – | – |
| user_ids | array | – | – |
| verification_date_range | object | – | – |
| verification_statuses | array | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
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
claude mcp add io-scalably-hunter-mcp -- npx -y @scalably-io/hunter-mcp
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 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 5 November 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.