author_finder
Find email addresses of article authors
LABSCO SUMMARY
Verification sits beside discovery, so an address can be checked before anything is sent to it.
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.
What it is
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.
What you get
- 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.
Requirements
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.
Setup effort
One command plus a key — npx -y @tomba-io/tomba-mcp-server, then supply credentials
USE CASES
01
Reaching a named person at a company you only know by domain
Derive the address from the domain and the name, then confirm it is deliverable before sending.
02
Turning a list of LinkedIn profiles into contactable people
The profile URL is often the only identifier a list carries, and it resolves to both an address and a number.
03
Working out who to approach at a company at all
Search the domain's addresses, and use the count to judge whether what you got back is the whole picture.
04
Qualifying a company before writing to it
What the site is built with and which companies resemble it decide whether the pitch fits.
05
Contacting the author of something you just read
The article itself is the starting point, not the company directory.
06
Cleaning a list before a campaign
Verify each address and enrich the ones that survive, rather than sending to all of them and watching bounces.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
companies_search
Search for companies using natural language queries with advanced filters
domain_search
Search emails based on domain name
email_count
Get the total number of email addresses for a domain
email_enrichment
Enrich email with additional data
email_finder
Find email address from domain, first name and last name
email_verifier
Verify email address deliverability
linkedin_finder
Find email addresses from LinkedIn URLs
phone_finder
Search phone numbers based on email, domain, or LinkedIn
phone_validator
Validate phone numbers and check carrier information
similar_finder
Find similar domains based on a specific domain
technology_finder
Instantly reveal the technology stack of any website
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected. The server also ships 7 resources and 16 prompts, such as find_contact and enrich_lead, which are not tools.
Requires
- npx on PATH
- Node.js 18 or later
- TOMBA_API_KEY in your environment
- TOMBA_SECRET_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @tomba-io/tomba-mcp-serverHosted endpoint
ENDPOINT URL
https://mcp.tomba.io/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"tomba": {
"command": "npx",
"args": [
"-y",
"@tomba-io/tomba-mcp-server"
],
"env": {
"TOMBA_API_KEY": "<YOUR_TOMBA_API_KEY>",
"TOMBA_SECRET_KEY": "<YOUR_TOMBA_SECRET_KEY>"
}
}
}
}
