Find the likely employer behind a Gmail or other free mail signup, with a confidence.
MCPpedia last refreshed this data
com.mambabuilt/mcp-personal-email-to-company-resolver is an MCP server that find the likely employer behind a Gmail or other free mail signup, with a confidence. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 61/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"mamba-personal-email-to-company-resolver": {
"env": {
"APIFY_TOKEN": "your-apify-token"
},
"args": [
"-y",
"@mambalabsdev/mcp-personal-email-to-company-resolver"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Find the likely employer behind a Gmail or other free mail signup, with a confidence.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@mambalabsdev/mcp-personal-email-to-company-resolver' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @mambalabsdev/mcp-personal-email-to-company-resolver against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in communication
Official TypeScript library for the Telnyx API
Open-source SMS gateway. Turn your Android phone into an SMS API: send and receive SMS from your apps over REST and webhooks. Self-hostable, with a free hosted plan.
Send email and newsletters with Mailtea over MCP, plus skills for email and website design.
X/Twitter automation MCP: scrape, post, schedule, analyze, engage. No API key required.
MCP Security Weekly
Get CVE alerts and security updates for com.mambabuilt/mcp-personal-email-to-company-resolver and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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.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.
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.
APIFY_TOKEN. The server lists its tool without a token; a call needs one.