Hatch MCP Server

MCP server for Hatch API integration. Features include finding emails, phone numbers, verifying emails, finding company data, and getting LinkedIn URLs. That is what the hatch mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• Find email addresses using first name, last name, and domain information
• Find phone numbers using LinkedIn profile URLs
• Verify if an email address is valid and active
• Find detailed information about a company using its domain
• Find LinkedIn URLs using name, designation, and company information

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 5 tools. What each one is for:

• hatch_find_email — Find an email address using first name, last name, and domain information
• hatch_find_phone — The hatch_find_phone tool exposed by this server
• hatch_verify_email — The hatch_verify_email tool exposed by this server
• hatch_find_company_data — The hatch_find_company_data tool exposed by this server
• hatch_get_linkedin_url — Find LinkedIn URL using name, designation, and company information

What it needs from you

Configuration is passed through the environment: HATCH_API_KEY, HATCH_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Hatch's toolset — hatch_find_email, hatch_find_phone, hatch_verify_email and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Meerkats-Ai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.