The finders start from different identifiers — a domain and a name, a LinkedIn URL, an article byline — which matters because what you actually hold varies from lead to lead. Deliverability is a separate call rather than a number attached to the guess, and phone numbers get the same treatment through a validator that also reports the carrier. The company-level tools answer the other half of qualifying a lead: what the business runs on and who resembles it, before anyone drafts a pitch.
A client for Tomba's email discovery, verification and enrichment API — 12 tools, 7 URI-templated resources and 16 pre-built prompt workflows covering the path from a company name to a verified contact.
- Every email address known for a domain, and a count of how many exist there in total — which is how you tell a complete list from a first page (domain_search, email_count).
- An address derived from a domain plus a first and last name, from a LinkedIn profile URL, or from an article's author byline (email_finder, linkedin_finder, author_finder).
- Deliverability verification as its own call rather than a confidence score bundled into the result, plus enrichment of an address with additional contact data (email_verifier, email_enrichment).
- Phone numbers searched from an email, a domain or a LinkedIn profile, then validated with carrier information (phone_finder, phone_validator).
- Company-level context: the technology stack a website runs on, and domains similar to one you name (technology_finder, similar_finder).
- Company search from a natural-language query with filters on headcount band, type, revenue band and industry (companies_search).
- Sixteen prompt workflows that chain the tools for common jobs — finding a complete contact, batch-verifying a list, researching a company, enriching a lead, analysing competitors, and generating leads from a market segment.
A Tomba account and both credentials — TOMBA_API_KEY in the ta_ form and TOMBA_SECRET_KEY in the ts_ form. Node.js 18 or higher for the local route, `npx -y @tomba-io/tomba-mcp-server` over stdio. A hosted endpoint at https://mcp.tomba.io/mcp is the alternative, authenticating with the two keys base64-encoded as a Bearer token. Note the package rename: configs pointing at the old `tomba-mcp-server` name need updating.
One command plus a key — npx -y @tomba-io/tomba-mcp-server, then supply credentials