Hunter
by Hunter Web Services, Inc. (Community)
Description
Find and organize companies without leaving ChatGPT. This app connects directly to Hunter to help you discover businesses that match your criteria, enrich them with reliable company-level data, and save the ones you care about. You can search for companies using natural language (for example, by location, industry, size, or technologies), review results with domain-level insights, and enrich any company to get structured information such as industry, headcount range, headquarters location, and tech stack. When a company looks relevant, you can save it straight to your Hunter Leads for later use. Designed for sales, marketing, and research workflows, the app focuses on fast exploration and clean company data. No personal data, no guesswork, just actionable company insights inside ChatGPT.
Capabilities
No special capabilities listed
AI Agent Discovery
Hunter is indexed by Tedix as a structured ai application listing for AI assistants, search crawlers, and users comparing agent-ready apps.
- Hunter is categorized as AI application.
- Developer: Hunter Web Services, Inc..
- Connector type: AI-Powered App.
- Current connector status: Connected.
- Observed distribution channels: chatgpt.
- Available regions: US, FR, GB, ES, IN.
Use this page to understand whether Hunter is relevant for ai application workflows in AI assistants.
For MCP discovery, this listing helps crawlers connect Hunter to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.
The canonical Tedix directory URL is https://tedix.dev/apps/hunter/.
Crawlable Profile
Source and availability
Tedix identifies Hunter from Upstream Mcp tool source; Store sources: ChatGPT app store; Distribution: Ecosystem Directory. Availability is reported for US, FR, GB, ES, IN.
- ChatGPT app store Auth required · RELEASED · US, FR, GB, ES, IN
Auth, tools, and actions
Authentication: Requires Login. No special capability flags are currently listed. Current MCP inventory reports 35 tools, 3 resources, and 3 prompts.
- Add-Campaign-Recipients · External-world action
Use this when the user wants to add recipients to an existing campaign by email address or by lead ID. Up to 50 per call; batch larger sets across multiple calls. Adding a recipient does not send email on its own — sending requires Start-Campaign. Free to call.
- Combined-Enrichment · External-world action
Use this when the user provides an email address or LinkedIn handle and wants both the person's profile and their company's profile in a single response. Costs 1 enrichment credit, only charged when data is found. Do not use this when the user only needs one side of the picture — call Person-Enrichment or Company-Enrichment directly to keep the response narrow.
- Company-Enrichment · External-world action
Use this when the user wants to look up a company by domain and see its industry, size, location, technologies, funding rounds, and social profiles. Does not return personal data (PII). Costs 1 enrichment credit, only charged when data is found. Do not use this for personal websites or webmail domains (gmail.com, yahoo.com, etc.) — there is no company behind those domains to enrich.
- Create-Custom-Attribute · App action
Use this when the user wants to define a new custom attribute on leads, identified by label. Free to call.
- Create-Lead · App action
Use this when the user wants to create a new lead in their Hunter account. Email is required; other fields are optional. Pass `leads_list_id` to add the lead directly to a list. Free to call.
- Create-Lead-If-Missing · App action
Use this when the user wants to save a verified contact as a new lead without modifying any existing lead. If a lead with the email already exists, returns the existing record unchanged with `alreadyExisted: true` and reports "already exists; no changes made"; otherwise creates the lead with the supplied fields. Never overwrites, never moves to a list, never enriches existing records. Use Create-Or-Update-Lead instead when the user explicitly wants to overwrite an existing lead. Free (no credits).
- Create-Leads-List · App action
Use this when the user wants to create a new, empty leads list with the given name. Free to call.
- Create-Or-Update-Lead · High-impact write action
Use this when the user explicitly wants to create a lead or overwrite an existing lead's fields by email. If a lead with the email exists, its fields are overwritten with the supplied values; otherwise a new lead is created. Free to call. Overwriting an existing lead's fields cannot be undone from the API. For save-without-overwrite semantics, use Create-Lead-If-Missing instead.
Plus 27 additional actions in the full tool inventory.
Verification freshness
- Catalog synced 11h ago (June 6, 2026)
- Connector checked 6d ago (May 31, 2026)
- MCP scanned 6d ago (May 31, 2026)
- Directory updated 11h ago (June 6, 2026)
Publisher Intelligence
Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.
Server Status Hunter ChatGPT v2.3.0
https://chatgpt.hunter.io/mcp Last checked: 6d ago
Technical Details
Tools(35)
Showing 35 of 35 tools
| Tool | Description | Flags | Test | Last Tested | |
|---|---|---|---|---|---|
Add-Campaign-Recipients | Use this when the user wants to add recipients to an existing campaign by email address or by lead ID. Up to 50 per call; batch larger sets across multiple calls. Adding a recipient does not send email on its own — sending requires Start-Campaign. Free to call. | — | 100%Latency 332ms | 5d ago | |
Combined-Enrichment | Use this when the user provides an email address or LinkedIn handle and wants both the person's profile and their company's profile in a single response. Costs 1 enrichment credit, only charged when data is found. Do not use this when the user only needs one side of the picture — call Person-Enrichment or Company-Enrichment directly to keep the response narrow. | — | 100%Latency 102ms | 5d ago | |
Company-Enrichment | Use this when the user wants to look up a company by domain and see its industry, size, location, technologies, funding rounds, and social profiles. Does not return personal data (PII). Costs 1 enrichment credit, only charged when data is found. Do not use this for personal websites or webmail domains (gmail.com, yahoo.com, etc.) — there is no company behind those domains to enrich. | — | 100%Latency 106ms | 5d ago | |
Create-Custom-Attribute | Use this when the user wants to define a new custom attribute on leads, identified by label. Free to call. | — | 100%Latency 117ms | 5d ago | |
Create-Lead | Use this when the user wants to create a new lead in their Hunter account. Email is required; other fields are optional. Pass `leads_list_id` to add the lead directly to a list. Free to call. | — | 100%Latency 63ms | 5d ago | |
Create-Lead-If-Missing | Use this when the user wants to save a verified contact as a new lead without modifying any existing lead. If a lead with the email already exists, returns the existing record unchanged with `alreadyExisted: true` and reports "already exists; no changes made"; otherwise creates the lead with the supplied fields. Never overwrites, never moves to a list, never enriches existing records. Use Create-Or-Update-Lead instead when the user explicitly wants to overwrite an existing lead. Free (no credits). | — | 100%Latency 65ms | 5d ago | |
Create-Leads-List | Use this when the user wants to create a new, empty leads list with the given name. Free to call. | — | 100%Latency 89ms | 5d ago | |
Create-Or-Update-Lead | Use this when the user explicitly wants to create a lead or overwrite an existing lead's fields by email. If a lead with the email exists, its fields are overwritten with the supplied values; otherwise a new lead is created. Free to call. Overwriting an existing lead's fields cannot be undone from the API. For save-without-overwrite semantics, use Create-Lead-If-Missing instead. | destructive | 100%Latency 55ms | 5d ago | |
Delete-Custom-Attribute | Use this when the user wants to permanently delete a custom-attribute definition, identified by ID. Per-lead values stored for the attribute are dropped and cannot be recovered. Free to call. | destructive | 100%Latency 55ms | 5d ago | |
Delete-Lead | Use this when the user wants to remove a lead from their Hunter account, identified by ID. Free to call. Deleting a lead cannot be undone from the API. | destructive | 100%Latency 81ms | 5d ago | |
Delete-Leads-List | Use this when the user wants to permanently delete a leads list, identified by ID. Lists with more than 10 leads are scheduled for asynchronous deletion (HTTP 202). Free to call. Deleting a list cannot be undone from the API. | destructive | 100%Latency 52ms | 5d ago | |
Domain-Search | Use this when the user wants the contacts published for a domain — emails with names, positions, and confidence scores. Optional filters: type, seniority, department, required field. Costs 1 search credit per 10 emails returned (rounded up), only charged when emails are found. Do not use this for personal/webmail domains (gmail.com, yahoo.com, etc.) — results will be empty. | — | 100%Latency 57ms | 5d ago | |
Email-Count | Use this when the user wants the count of email addresses Hunter has indexed for a domain, optionally split by personal vs generic. Free to call. Do not use this as a substitute for Domain-Search; this returns a count only, not the email list itself. | read-only | 100%Latency 53ms | 5d ago | |
Email-Finder | Use this when the user wants a specific person's email address at a company. Provide the person's full name and the company's domain. Costs 1 search credit, only charged when an email is found. Do not use this when the user already has the email and only wants to confirm it works — call Email-Verifier instead. | — | 100%Latency 62ms | 5d ago | |
Email-Verifier | Use this when the user wants to check whether an email address is deliverable. Returns a status (valid, invalid, accept_all, etc.) and a confidence score. Costs 1 verification credit, only charged for valid, invalid, or accept_all results. Do not use this on role/group addresses (info@, support@, etc.) — deliverability of role addresses is not meaningful and the result will typically be accept_all. | — | 100%Latency 77ms | 5d ago | |
Find-Companies | Use this when the user wants to search for companies that match natural-language criteria such as location, industry, size, type, or technologies. Returns up to 100 matching companies per page; use `offset` to paginate. The response includes `meta.permalink` — a link to the same query on hunter.io that the user can open to view all results with the inferred filters applied. Free to call. Do not use this when the user has already named a specific company — call Company-Enrichment directly with that company's domain. | read-only | 100%Latency 95ms | 5d ago | |
Get-Account-Details | Use this when the user asks about their Hunter plan or remaining credits. Returns plan name and per-product credit balances (search, verification, enrichment). Does not return personal identifiers such as name, email, or team ID. Free to call. | read-only | 100%Latency 79ms | 5d ago | |
Get-Custom-Attribute | Use this when the user wants to retrieve a single custom-attribute definition by ID. Free to call. | read-only | 100%Latency 54ms | 5d ago | |
Get-Lead | Use this when the user wants to retrieve a single lead from their Hunter account by ID. Free to call. | read-only | 100%Latency 53ms | 5d ago | |
Get-Leads-List | Use this when the user wants to retrieve a single leads list (name, lead count, timestamps) by ID. Free to call. | read-only | 100%Latency 69ms | 5d ago | |
Lead-Exists | Use this when the user wants to check whether a lead with a given email already exists in their Hunter account. Returns the lead ID and list info if present. Free to call. | read-only | 100%Latency 73ms | 5d ago | |
List-Campaign-Recipients | Use this when the user wants to list the recipients of a campaign with per-recipient status. Free to call. | read-only | 100%Latency 70ms | 5d ago | |
List-Campaigns | Use this when the user wants to list the campaigns in their Hunter account with name, status, and counts. Campaigns are created in the Hunter web UI; the API can list them, manage recipients, and start them. Free to call. | read-only | 100%Latency 87ms | 5d ago | |
List-Custom-Attributes | Use this when the user wants to list all custom attributes defined on leads in their Hunter account. Free to call. | read-only | 100%Latency 67ms | 5d ago | |
List-Leads | Use this when the user wants to list leads from their Hunter account, with optional filters on email, name, company, or list. Returns up to 100 leads per page; use `offset` to paginate. Free to call. | read-only | 100%Latency 51ms | 5d ago | |
List-Leads-Lists | Use this when the user wants to list the leads lists in their Hunter account, with pagination. Free to call. | read-only | 100%Latency 100ms | 5d ago | |
Merge-Leads-Lists | Use this when the user wants to move every lead from a source list into a destination list. The source list is permanently deleted after the move. Leads on the destination list are preserved. Free to call. Merging cannot be undone from the API. | destructive | 100%Latency 49ms | 5d ago | |
Person-Enrichment | Use this when the user wants to look up a professional contact by email address and see their name, job title, employer, location, phone number, and social profiles. Costs 1 enrichment credit, only charged when data is found. Do not use this for consumer profiles — Hunter's enrichment covers business contacts. | — | 100%Latency 189ms | 5d ago | |
Plan-Prospecting-Flow | Use this when the user gives a natural-language prospecting brief (e.g. "Find 20 marketing leads at fintech companies in Berlin") and wants a step-by-step plan for finding companies, contacts, verifying emails, and saving leads. Returns the plan plus a first action so the model can execute the chain end to end. Free to call; sub-tools charge their own credits. | read-only | 100%Latency 55ms | 5d ago | |
Remove-Campaign-Recipients | Use this when the user wants to remove recipients from a campaign by email address. Pending messages scheduled for the removed recipients are cancelled; messages already sent are not recalled. Free to call. | destructive | 100%Latency 47ms | 5d ago | |
Save-Company | Use this when the user wants to add a company as a lead in their Hunter account, identified by domain. Free to call. | — | 100%Latency 80ms | 5d ago | |
Start-Campaign | Use this when the user wants to start an existing campaign, which begins sending real emails to its recipients. The campaign must have a subject, message body, and connected email account configured in the Hunter UI. Free to call. Starting a campaign sends real emails to recipients and requires an explicit user confirmation: the first call returns a confirmation prompt without sending, and only re-issuing with `confirmed: true` actually starts the campaign. | destructive | 100%Latency 53ms | 5d ago | |
Update-Custom-Attribute | Use this when the user wants to rename an existing custom-attribute definition, identified by ID. Overwrites the existing label; the previous label cannot be recovered from the API. If the user declines the rename, offer to instead create a new custom-attribute definition with the desired label. Free to call. | destructive | 100%Latency 68ms | 5d ago | |
Update-Lead | Use this when the user wants to update fields on an existing lead identified by ID. Free to call. Updating a lead overwrites the supplied fields in place. | destructive | 100%Latency 63ms | 5d ago | |
Update-Leads-List | Use this when the user wants to rename an existing leads list, identified by ID. Overwrites the existing list name; the previous name cannot be recovered from the API. If the user declines the rename, offer to instead create a new leads list with the desired name. Free to call. | destructive | 100%Latency 53ms | 5d ago |
Discoverability Score
Fair
61 of 100 — how easily AI agents find your app
- Description quality20/20
- Example prompts0/20
- Keyword coverage0/15
- Tool metadata20/20
- Visual assets8/20
- Endpoint health10/10
- Data freshness15/15
How to Improve
Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.
Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.
Add at least 2 screenshots that show real workflows to increase confidence and conversion.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Requires Login
- Listed on
- ChatGPT
- Added
- May 30, 2026
- Last synced
- 11h ago
- Last checked
- 6d ago
- Version
- 2.3.0
- Distribution
- Ecosystem Directory