Mcp Personal Email To Company Resolver

com.mambabuiltPublished by mambabuilt.comv1.0.1Updated Nov 7, 2026

Find the likely employer behind a Gmail or other free mail signup, with a confidence.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Resolves the likely employer behind a free consumer email address (Gmail, Outlook and similar) using public Gravatar, GitHub and LinkedIn signals, with a…

What you can do
  • Resolve employers for one address or up to 300 addresses at once
  • Return one row per address with the person's name, likely employer, employer domain and a confidence value
  • Report where the employer came from (Gravatar, GitHub, web result, LinkedIn headline or email domain) with evidence links
  • Optionally add one exact web search per unresolved address and run a LinkedIn URL resolver step
When to use it
Useful when you have signups, leads or contact lists with personal mail addresses and want a best guess at which company each person works for, with evidence and a confidence level to filter on.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. An Apify account and an Apify API token set as APIFY_TOKEN are required for calls; the tool is listed without one. Network access to Apify is needed, and an optional GitHub token can be supplied.
Before you install
Each call spends money on your Apify account: resolved addresses and run starts are billed per event, and the optional LinkedIn resolver bills per person sent, found or not. The optional GitHub token is passed through for the run. It infers employers from public profiles, so results are probabilistic and may be wrong; a cost cap input is available.

Installation

In SourceWeft

  1. Open Mcp Personal Email To Company Resolver in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Personal Email to Company Resolver MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Personal Email To Company Resolver MCP server]

Give it a free mail address (Gmail, Outlook, iCloud, Yahoo, and about 140 more consumer domains). Each run reads the public Gravatar profile for the address, the GitHub account whose public commits are signed with it, and, for a name with an employer, Mamba Labs Person LinkedIn URL Resolver. It returns one row per address with the person's name, likely employer, employer domain, and a confidence. It never contacts the mailbox and never opens LinkedIn.

What's Inside

What it does

  • match_status is resolved (employer at 0.75 or more, billed), weak, name_only, corporate_email, not_found, invalid_email, or blocked, and only resolved is billed.
  • employer_source says where the employer came from: gravatar, github, web_result, linkedin_headline, or email_domain. evidence_urls lists the public pages.
  • The LinkedIn step raises the confidence when a LinkedIn result shows the employer as current and lowers it when it shows it as former.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-personal-email-to-company-resolver": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-personal-email-to-company-resolver"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The resolve_personal_email_employer tool appears.

Prerequisites

Example prompts

  • "These ten signups used Gmail addresses. Which companies do they work at?"
  • "Find the employer behind this Outlook address and show me the evidence."

Tool

resolve_personal_email_employer. One tool. Example arguments:

json
{ "emails": ["[email protected]"] }

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults.

InputTypeDescription
emailstringOne address
emailsarrayUp to 300 addresses
github_tokenstringOptional, your own free GitHub token
search_webstringtrue adds one exact Google search per address left without an employer. Default false
use_linkedin_resolverstringtrue (default) runs Person LinkedIn URL Resolver from your account, billed at its own price
countrystringGoogle country code. Default us
max_charge_usdstringOptional cost cap for the run

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
email-resolved, per address with an employer at 0.75 or more$0.025$0.02375$0.0225$0.02125
apify-actor-start, per run start$0.0005$0.0005$0.0005$0.0005

Every other row is free. With use_linkedin_resolver on, Person LinkedIn URL Resolver bills its own events on top: $0.035 per person sent to it, found or not, plus $0.0005 per run on the free plan.

Your keys

The actor holds no key. github_token is optional and is your own, used for the run only. Mamba Labs pays the platform costs of the run, proxy traffic included.

Full actor documentation

apify.com/mambalabs/personal-email-to-company-resolver

License

MIT. See LICENSE.

Source: README.md at commit 7d7b46e

Tools

1

resolve_personal_email_employer

Resolve the employer behind a personal email

Find the likely employer behind a free mail address (Gmail, Outlook, iCloud, Yahoo, and about 140 more), from the public Gravatar profile for the address, the GitHub account whose public commits are signed with it, and Mamba Labs Person LinkedIn URL Resolver. Returns one row per address with person_name, employer_name, employer_domain when a source names it, employer_source, employer_confidence from 0 to 1, match_status (resolved at 0.75 or more, weak, name_only, corporate_email, not_found, invalid_email, blocked), the LinkedIn URL when found, and evidence_urls. It never contacts the mailbox and never opens LinkedIn. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per resolved address, and the optional LinkedIn step is billed by Person LinkedIn URL Resolver at its own price.

Parametersemailemailscountrysearch_webgithub_tokenmax_charge_usduse_linkedin_resolver

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Oct 22, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts