Hatch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HATCH_API_KEY | Yes | Your Hatch API key | |
| HATCH_API_URL | No | Custom API URL (defaults to https://api.hatchhq.ai) | |
| HATCH_RETRY_MAX_DELAY | No | Maximum delay in milliseconds for retries (default: 10000) | |
| HATCH_RETRY_MAX_ATTEMPTS | No | Maximum retry attempts for API calls (default: 3) | |
| HATCH_RETRY_INITIAL_DELAY | No | Initial delay in milliseconds for retries (default: 1000) | |
| HATCH_RETRY_BACKOFF_FACTOR | No | Backoff factor for retry delays (default: 2) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hatch_find_emailB | Find an email address using first name, last name, and domain information. |
| hatch_find_phoneB | Find a phone number using LinkedIn profile URL. |
| hatch_verify_emailC | Verify if an email address is valid and active. |
| hatch_find_company_dataB | Find detailed information about a company using its domain. |
| hatch_get_linkedin_urlC | Find LinkedIn URL using name, designation, and company information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose targeting different data types: company data, email, phone, LinkedIn URL, and email verification. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the specific need.
All tools follow a consistent 'hatch_verb_noun' pattern (e.g., hatch_find_company_data, hatch_verify_email). The naming is uniform, using snake_case throughout, which enhances predictability and readability.
With 5 tools, the server is well-scoped for its purpose of data lookup and verification. Each tool serves a specific, non-redundant function, making the count appropriate and manageable for the domain.
The toolset covers key data lookup operations (company, email, phone, LinkedIn URL) and email verification, providing a solid foundation. A minor gap might be the lack of a tool for updating or managing retrieved data, but the core functionality is complete for the stated purpose.