email-discoverylead-enrichmentcompany-researchdata-extraction
Connects MCP clients to Tomba.io for email discovery, verification, contact enrichment, company research, and domain intelligence.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Find contact emails from names, domains, articles, or LinkedIn profiles
Verify email deliverability before outreach
Enrich leads with person and company data
Research company domains, competitors, and technology stacks
Validate phone numbers and retrieve carrier information
Key features
Email discovery and domain search
Email and phone verification
Person and company enrichment
Natural-language company search
Domain and technology intelligence
Lead and account management
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Tomba MCP Server.
Extracted Tool Capabilities
Email discovery and domain search
Email and phone verification
Person and company enrichment
Natural-language company search
Domain and technology intelligence
Lead and account management
How Tomba MCP Server works
What tomba-io/tomba-mcp-server MCP server does
The tomba-io/tomba-mcp-server MCP server connects an MCP-compatible client to the Tomba.io API. Its capabilities cover contact discovery, email validation, enrichment, company research, and domain analysis. The API account supplies the underlying data, while the MCP layer makes those operations available to an agent through standardized tools, resources, and prompts.
Email-focused operations include searching a domain for addresses, generating a likely address from a person and domain, finding authors or LinkedIn contacts, checking email sources and domain patterns, and counting addresses. Verification can check deliverability and whether an address appears in Tomba’s database. Enrichment tools return available person or company details, including items such as role, social profiles, industry, company size, and location.
Additional operations cover phone lookup and validation, disposable or webmail domain checks, company-name autocomplete, similar-domain discovery, technology-stack detection, employee location counts, natural-language company search, lead management, account information, usage, API keys, flags, and request logs.
How it works
The server exposes 28 tools, seven URI resources, and 16 pre-built prompts. Resources provide addressable views such as tomba://email/{email}, tomba://domain/{domain}, similar-domain results, technology information, API status, and documentation. Prompts organize multi-step activities including contact finding, list verification, lead enrichment, journalist research, competitor analysis, technology audits, market research, and company targeting.
stdio is the default transport and is intended for local MCP client configuration. An HTTP mode is also available and provides REST endpoints. API requests use live Tomba infrastructure. Calls have a 120-second timeout, and the server retries rate-limit and server-error responses up to three times with delays of one, two, and four seconds.
Setup and configuration
Running the tomba-io/tomba-mcp-server MCP server requires Node.js 18 or newer, npm or Yarn, and a Tomba API account. The published package is @tomba-io/tomba-mcp-server; the README notes that it replaced the older tomba-mcp-server package name.
For a stdio setup, run the package with npx -y @tomba-io/tomba-mcp-server and provide these environment variables:
TOMBA_API_KEY: the Tomba API key.TOMBA_SECRET_KEY: the Tomba secret key.
The README shows this configuration for Claude Desktop on both macOS/Linux and Windows. Source installation is also documented: clone the repository, run yarn install, and build with yarn build.
Tools and capabilities
Use the discovery tools to locate addresses by domain, name, article author, or LinkedIn URL. Use verification and validation tools before relying on email or phone contact data. Enrichment operations can combine person and company information, while company search supports natural-language queries and filters for size, type, revenue, and industry.
Account and operational tools expose plan, credit, usage, submitted data flags, leads, API keys, and recent request logs. The service documents plan-based rate limits: the free plan allows one request per second, two per minute, and five per day, while higher plans provide larger limits. Requests that produce no result do not consume credits, and duplicate requests within 30 days are not counted again.
Limitations and notes
The tomba-io/tomba-mcp-server MCP server depends on a Tomba account and its API credentials. Results and response times depend on the target company’s SMTP server, website responsiveness, and the requested catch-all detection depth. Rate limits vary by Tomba plan and endpoint, so bulk workflows should account for those limits.
The supplied material explicitly documents Claude Desktop configuration and stdio operation. It does not establish compatibility with every other MCP client. The README also mentions an OpenClaw skill in the repository, but the provided excerpt does not document its full behavior or configuration.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
8
Stargazers on the source repository.
npm downloads
454
Package downloads in the last 30 days.
Last commit
8d ago
Most recent push to the default branch.
Directory activity
3 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Tomba MCP Server
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/tomba-io-tomba-mcp-server)HTML Embed
<a href="https://allmcps.com/mcp/tomba-io-tomba-mcp-server"><img src="https://allmcps.com/api/badge/tomba-io-tomba-mcp-server?style=directory" alt="Tomba MCP Server on AllMCPs" /></a>Technical Specs & Signals
CategoryMarketing
PricingFreemium
8/9 checks healthy over the last 31d
56Quality signal: Good · 56/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools24/30
Adoption & activity8/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 18d ago via OSV.dev · @tomba-io/tomba-mcp-server (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.