com.mambabuilt/mcp-personal-email-to-company-resolver
Find the likely employer behind a Gmail or other free mail signup, with a confidence.
Que pouvez-vous faire avec com.mambabuilt/mcp-personal-email-to-company-resolver ?
match_statusisresolved(employer at 0.75 or more, billed),weak,name_only,corporate_email,not_found,invalid_email, orblocked, and onlyresolvedis billed.employer_sourcesays where the employer came from:gravatar,github,web_result,linkedin_headline, oremail_domain.evidence_urlslists 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.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@mambalabsdev/mcp-personal-email-to-company-resolverclaude mcp add mcp-personal-email-to-company-resolver -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-personal-email-to-company-resolver@1.0.0
{
"mcpServers": {
"mcp-personal-email-to-company-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-personal-email-to-company-resolver@1.0.0"
],
"env": {
"APIFY_TOKEN": "<your apify_token>"
}
}
}
}
Variables d'environnement
APIFY_TOKENobligatoire secret Apify API token from https://console.apify.com/account/integrations
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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
- Quick start
- Prerequisites
- Example prompts
- Tool
- Inputs
- Pricing
- Your keys
- Full actor documentation
- License
What it does
match_statusisresolved(employer at 0.75 or more, billed),weak,name_only,corporate_email,not_found,invalid_email, orblocked, and onlyresolvedis billed.employer_sourcesays where the employer came from:gravatar,github,web_result,linkedin_headline, oremail_domain.evidence_urlslists 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:
{
"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
- Node.js 18 or newer.
- An Apify API token from console.apify.com/account/integrations, set as
APIFY_TOKEN. The server lists its tool without a token; a call needs one.
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:
{ "emails": ["sample.signup@gmail.com"] }
Inputs
Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults.
| Input | Type | Description |
|---|---|---|
email | string | One address |
emails | array | Up to 300 addresses |
github_token | string | Optional, your own free GitHub token |
search_web | string | true adds one exact Google search per address left without an employer. Default false |
use_linkedin_resolver | string | true (default) runs Person LinkedIn URL Resolver from your account, billed at its own price |
country | string | Google country code. Default us |
max_charge_usd | string | Optional cost cap for the run |
Pricing
Pay per event on Apify, billed to your Apify account. Prices in USD.
| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
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.
Questions fréquentes
Qu'est-ce que com.mambabuilt/mcp-personal-email-to-company-resolver ?
Find the likely employer behind a Gmail or other free mail signup, with a confidence.
Comment installer com.mambabuilt/mcp-personal-email-to-company-resolver ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add mcp-personal-email-to-company-resolver -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-personal-email-to-company-resolver@1.0.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour com.mambabuilt/mcp-personal-email-to-company-resolver ?
Oui. Il attend APIFY_TOKEN, à renseigner dans sa configuration.
com.mambabuilt/mcp-personal-email-to-company-resolver est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient com.mambabuilt/mcp-personal-email-to-company-resolver ?
Il est publié par mambalabsdev. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.