Open-Source Cold Email & Warmup Platform
Warmbly 是开源的冷邮件平台:温暖您的邮箱、发送活动、并对每条回复进行分流。可在我们的云端运行,也可自行托管整套系统。
AI 翻译
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证Hunter.io MCP server: domain search, email finder and verifier, enrichment, discovery, leads. Runs in production at Scalably.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Hunter.io MCP server. 11 tools cover domain search, email finding and verification, enrichment, company discovery, and lead management.
Claude Desktop: download hunter-mcp.mcpb from the latest GitHub release and open it.
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.查看完整 README ↗Hunter.io MCP server. 11 tools cover domain search, email finding and verification, enrichment, company discovery, and lead management.
Claude Code:
claude mcp add hunter -e HUNTER_API_KEY=your-key -- npx -y @scalably-io/hunter-mcp
Codex:
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.
create_lead writes to your Hunter leads list and is the only non-read tool; the other 10 tools are read-only.| Tool | What it does |
|---|---|
account_info | Read the Hunter v2 account plan and exact current credit usage, including remaining unified or per-type balances |
domain_search | Search Hunter v2 emails for one domain/company with current people, verification, location, job-title, decision-maker, aggregation, and offset filters |
email_finder | Find and automatically verify the most likely professional email from a company/domain plus name, or directly from a LinkedIn handle |
email_verifier | Verify one email address with Hunter v2 and return exact deliverability, score, SMTP/MX, accept-all, webmail, disposable, and source evidence |
email_count | Count Hunter email coverage for a domain/company, optionally limited to personal or generic addresses, without returning addresses |
email_enrichment | Enrich a person from an email address or LinkedIn handle using Hunter v2, optionally in Clearbit-compatible format |
company_enrichment | Enrich a company from its domain using Hunter v2, optionally in Clearbit-compatible format |
combined_enrichment | Enrich both a person and their company from one email using Hunter v2, optionally in Clearbit-compatible format |
discover | Use Hunter Discover v2 to find companies from current natural-language or structured organization, location, industry, headcount, type, year, keyword, technology, and funding filters |
create_lead | Create one Hunter lead from a required email and optional current lead fields, list placement, and custom attributes. This is a single-attempt mutation |
list_leads | List Hunter leads with current list, identity, company, status, verification, activity/date, location, tag, campaign, user, confidence, custom-attribute, query, and offset filters |
| Variable | Required | Purpose |
|---|---|---|
HUNTER_API_KEY | yes | Hunter.io API key from hunter.io/api-keys |
HUNTER_API_BASE | no | Override the Hunter API base URL (default https://api.hunter.io/v2) |
HUNTER_TIMEOUT_MS | no | Per-request timeout in milliseconds (default 30000) |
HUNTER_RETRY_BASE_MS | no | Base delay in milliseconds for the GET retry backoff (default 500) |
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>.
Hunter's per-plan request quotas surface in account_info.
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.
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
MIT. Copyright Scalably.