Tomba MCP Server
REMOTE · MCP.TOMBA.IO · 2 COMPONENTS · SCANNED OCT 2
MCP server for Tomba email finder, verification, and contact enrichment API
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Tomba MCP Server server?
Tomba MCP Server is a hosted endpoint at https://mcp.tomba.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.tomba.io
claude mcp add --transport http tomba-io-tomba-mcp-server 'https://mcp.tomba.io/mcp'
{
"mcpServers": {
"tomba-io-tomba-mcp-server": {
"url": "https://mcp.tomba.io/mcp"
}
}
} {
"servers": {
"tomba-io-tomba-mcp-server": {
"type": "http",
"url": "https://mcp.tomba.io/mcp"
}
}
} [mcp_servers.tomba-io-tomba-mcp-server] url = "https://mcp.tomba.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tomba-io-tomba-mcp-server": {
"type": "remote",
"url": "https://mcp.tomba.io/mcp",
"enabled": true
}
}
} openclaw mcp add tomba-io-tomba-mcp-server --url 'https://mcp.tomba.io/mcp' --transport streamable-http
mcp_servers:
tomba-io-tomba-mcp-server:
url: "https://mcp.tomba.io/mcp" {
"McpServers": {
"tomba-io-tomba-mcp-server": {
"Transport": "http",
"Url": "https://mcp.tomba.io/mcp"
}
}
} assistant mcp add tomba-io-tomba-mcp-server -t streamable-http -u 'https://mcp.tomba.io/mcp'
{
"mcpServers": {
"tomba-io-tomba-mcp-server": {
"type": "http",
"url": "https://mcp.tomba.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 −41
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 6 Sept 26 +1
- Stability: 0.97 → pass security
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 78
- Tool coverage: 100% → 75% ▼ functional
- Schema quality: 72 → 56 ▲ functional
- Tool “mpp_email_verifier” now declares an output schema ▲ functional
- Tool “mpp_linkedin_finder” now declares an output schema ▲ functional
- Tool “mpp_phone_finder” now declares an output schema ▲ functional
- Tool “mpp_phone_validator” now declares an output schema ▲ functional
- Tool “mpp_similar_finder” now declares an output schema ▲ functional
- Tool “phone_finder” now declares an output schema ▲ functional
- Tool “phone_validator” now declares an output schema ▲ functional
- Tool “similar_finder” now declares an output schema ▲ functional
- Tool “technology_finder” now declares an output schema ▲ functional
- Tool “author_finder” now declares an output schema ▲ functional
- Tool “companies_search” now declares an output schema ▲ functional
- Tool “domain_search” now declares an output schema ▲ functional
- Tool “email_count” now declares an output schema ▲ functional
- Tool “email_enrichment” now declares an output schema ▲ functional
- Tool “email_finder” now declares an output schema ▲ functional
- Tool “email_verifier” now declares an output schema ▲ functional
- Tool “linkedin_finder” now declares an output schema ▲ functional
- Tool “mpp_author_finder” now declares an output schema ▲ functional
- Tool “mpp_domain_search” now declares an output schema ▲ functional
- Tool “mpp_email_count” now declares an output schema ▲ functional
- Tool “mpp_email_enrichment” now declares an output schema ▲ functional
- Tool “mpp_email_finder” now declares an output schema ▲ functional
- The server now declares the “logging” capability functional
- First check of Tool coverage: 100 functional
- Schema quality: excellent → good functional
- New tool “account_info” functional
- New tool “autocomplete” functional
- New tool “combined_enrichment” functional
- New tool “company_enrichment” functional
- New tool “create_flag” functional
- New tool “create_lead” functional
- New tool “domain_status” functional
- New tool “email_format” functional
- New tool “email_sources” functional
- New tool “get_logs” functional
- New tool “list_keys” functional
- New tool “list_leads” functional
- New tool “location” functional
- New tool “person_enrichment” functional
- New tool “usage_info” functional
- New tool “list_flags” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 2 Oct 2026 · Probed https://mcp.tomba.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tomba.io | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5509cdc4097f79f0ed11e95820cc5e9f105 |
| SANs: *.tomba.io, tomba.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.tomba.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| tomba.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.tomba.io/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.tomba.io/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| www-authenticate | Bearer resource_metadata="https://mcp.tomba.io/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.tomba.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.tomba.io/mcp |
| Authorisation server | https://api.tomba.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tomba.io/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.tomba.io/mcp | HTTPS enforced | 301 | https://mcp.tomba.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_info Account Info ~23
Get current Tomba account information including plan, credits, and usage limits
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
author_finder Author Finder ~62
Find the email address of an article's author from a given URL. Useful for outreach to content creators and journalists.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL of the article or blog post |
| webhook_url | string | – | Optional webhook URL to receive results asynchronously |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
autocomplete Autocomplete ~25
Autocomplete company names and retrieve logo and domain information
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
combined_enrichment Combined Enrichment ~24
Combined person and company enrichment by email
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
companies_search Companies Search ~129
Search for companies in the Tomba database. Filter by name, industry, country, and more to find target companies for outreach.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Filter options with include/exclude arrays for: location_country, location_city, location_state, industry, size, type, keywords, founded, technologies, similar, revenue, sic, naics |
| page | number | – | Page number for pagination (1-1000) |
| query | string | – | Search query for company name or keywords (8-100 characters) |
| webhook_url | string | – | Optional webhook URL to receive results asynchronously |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
company_enrichment Company Enrichment ~42
Find company data by domain including industry, size, location, and social profiles
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name (e.g., 'stripe.com') |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
create_flag Create Flag ~44
Report incorrect data for credit recovery
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | – |
| flag_type | string | yes | – |
| reason | string | yes | – |
| value | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
create_lead Create Lead ~62
Add a new lead to a list
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| string | yes | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| list_id | integer | yes | – |
| position | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
domain_search Domain Search ~179
Search for all email addresses associated with a specific domain or company. Returns a list of email addresses found for the given company domain along with metadata about each contact.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The company name to search for |
| country | string | – | Filter by country code (e.g., 'US', 'GB') |
| department | string | – | Filter by department (e.g., 'executive', 'it', 'marketing') |
| domain | string | – | The domain to search for emails (e.g., 'example.com') |
| enrich_mobile | boolean | – | Whether to enrich with mobile phone data |
| limit | string | – | Maximum number of results to return (10, 20, or 50) |
| page | number | – | Page number for pagination |
| webhook_url | string | – | Optional webhook URL to receive results asynchronously |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
domain_status Domain Status ~39
Check if a domain is a webmail provider or disposable email service
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name (e.g., 'stripe.com') |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
email_count Email Count ~53
Get the count of email addresses available for a specific domain. Useful for estimating the potential reach before performing a full domain search.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to count emails for (e.g., 'example.com') |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
email_enrichment Email Enrichment ~46
Enrich an email address with additional information about the person, including their name, position, company details, and social profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to enrich |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
email_finder Email Finder ~152
Find the email address of a specific person given their name and company domain or company name. Uses various techniques to generate and verify the most likely email format.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The company name to search in |
| domain | string | – | The domain of the company (e.g., 'example.com') |
| enrich_mobile | boolean | – | Whether to enrich with mobile phone data |
| first_name | string | – | The first name of the person |
| full_name | string | – | The full name of the person (alternative to first_name/last_name) |
| last_name | string | – | The last name of the person |
| webhook_url | string | – | Optional webhook URL to receive results asynchronously |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
email_format Email Format ~36
Get the email format patterns used by a specific domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name (e.g., 'stripe.com') |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
email_sources Email Sources ~26
Find where an email address was found on the web
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
email_verifier Email Verifier ~78
Verify if an email address is valid and deliverable. Checks for proper format, domain validity, and mailbox existence without sending an email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify | |
| enrich_mobile | boolean | – | Whether to enrich with mobile phone data |
| webhook_url | string | – | Optional webhook URL to receive results asynchronously |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
get_logs Get Logs ~28
Get recent API request logs
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| page | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
linkedin_finder Linkedin Finder ~72
Find the email address associated with a LinkedIn profile URL. Extracts contact information from LinkedIn profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| enrich_mobile | boolean | – | Whether to enrich with mobile phone data |
| url | string | yes | The LinkedIn profile URL |
| webhook_url | string | – | Optional webhook URL to receive results asynchronously |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
list_flags List Flags ~33
List submitted data flags with status and credit refund information
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
list_keys List Keys ~16
List all API keys for the account
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
list_leads List Leads ~37
List leads with optional domain filter
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| limit | number | – | – |
| page | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
location Location ~34
Get employees location count by country for a domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name (e.g., 'stripe.com') |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_author_finder Mpp Author Finder ~56
Find the email address of the author of a blog post or article using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL of the article or blog post |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_domain_search Mpp Domain Search ~144
Search for all email addresses associated with a specific domain using MPP (Machine Payments Protocol). Pay-per-request, no API key required — only an InFlow buyer key.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The company name to search for |
| country | string | – | Filter by country code (e.g., 'US', 'GB') |
| department | string | – | Filter by department (e.g., 'executive', 'it', 'marketing') |
| domain | string | – | The domain to search for emails (e.g., 'example.com') |
| limit | string | – | Maximum number of results to return |
| page | number | – | Page number for pagination |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_email_count Mpp Email Count ~51
Get the count of email addresses available for a specific domain using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to count emails for |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_email_enrichment Mpp Email Enrichment ~51
Enrich an email address with detailed contact and company information using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to enrich |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_email_finder Mpp Email Finder ~97
Find a person's email address given their name and company domain using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The company name |
| domain | string | – | The domain of the company |
| first_name | string | – | The first name |
| full_name | string | – | The full name of the person |
| last_name | string | – | The last name |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_email_verifier Mpp Email Verifier ~50
Verify if an email address is valid and deliverable using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_linkedin_finder Mpp Linkedin Finder ~52
Find a person's email address from their LinkedIn profile URL using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The LinkedIn profile URL |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_phone_finder Mpp Phone Finder ~93
Find phone numbers associated with an email address, domain, or LinkedIn profile using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The domain to look up |
| string | – | The email address to look up | |
| full | boolean | – | Whether to return full phone details |
| string | – | The LinkedIn profile URL |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_phone_validator Mpp Phone Validator ~54
Validate a phone number and get carrier and location details using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | The phone number to validate in E.164 format |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
mpp_similar_finder Mpp Similar Finder ~50
Find domains similar to a given domain using MPP (Machine Payments Protocol). Pay-per-request, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to find similar domains for |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
person_enrichment Person Enrichment ~32
Find person data by email including name, position, company, and social profiles
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
phone_finder Phone Finder ~104
Find phone numbers associated with an email address, domain, or LinkedIn profile. Returns direct and company phone numbers when available.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Domain to search for phone numbers |
| string | – | Email address to search for phone numbers | |
| full | boolean | – | Whether to return full phone details |
| string | – | LinkedIn URL to search for phone numbers | |
| webhook_url | string | – | Optional webhook URL to receive results asynchronously |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
phone_validator Phone Validator ~60
Validate and get information about a phone number. Returns the carrier, line type, country, and whether the number is valid.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | The phone number to validate (E.164 format recommended, e.g., +14155552671) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
similar_finder Similar Finder ~56
Find companies similar to a given domain. Returns a list of competitor or similar businesses based on industry, size, and other factors.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to find similar companies for (e.g., 'example.com') |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
technology_finder Technology Finder ~53
Discover the technologies used by a website. Returns information about the tech stack including CMS, frameworks, analytics, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to analyze for technologies (e.g., 'example.com') |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
usage_info Usage Info ~17
Get current API usage statistics across all endpoints
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
What is the Tomba MCP Server server?
Tomba MCP Server is listed in the public MCP registry as io.github.tomba-io/tomba-mcp-server. MCP server for Tomba email finder, verification, and contact enrichment API. This page covers its hosted endpoint (https://mcp.tomba.io/mcp).
Is the Tomba MCP Server server safe to use?
Tomba MCP Server scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tomba MCP Server server expose?
Tomba MCP Server exposes 38 tools: account_info, author_finder, autocomplete, combined_enrichment, companies_search, and 33 more. Their descriptions and schemas cost roughly 2,260 tokens of context every time the server is loaded.
Does the Tomba MCP Server server require authentication?
Yes. Tomba MCP Server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Tomba MCP Server server still maintained?
Tomba MCP Server is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.