com.mambabuilt/mcp-personal-email-to-company-resolver
NPM · @MAMBALABSDEV/MCP-PERSONAL-EMAIL-TO-COMPANY-RESOLVER
Find the likely employer behind a Gmail or other free mail signup, with a confidence.
Available components
Last scanned (10 hours ago)
Scores higher than 39% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 424 tokens (~424/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 69
First indexed and scored.
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 23 Oct 2026 · Analysed npm/@mambalabsdev/mcp-personal-email-to-company-resolver@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
resolve_personal_email_employer Resolve the employer behind a personal email ~424
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two letter Google country code. Default us. |
| string | – | One email address, for example a signup on a Gmail address. | |
| emails | array | – | Several addresses, up to 300. A company address returns its own domain, free. |
| github_token | string | – | Optional. Your own free GitHub token, for batches over about 25 addresses. Used for this run only and never stored. |
| max_charge_usd | string | – | Optional. The run stops before a charge that would pass this amount; it is passed to the LinkedIn step too. |
| search_web | string | – | true adds one exact Google search for an address that Gravatar and GitHub leave without an employer. Default false. |
| use_linkedin_resolver | string | – | true (default) runs Mamba Labs Person LinkedIn URL Resolver from your account for the addresses with a name and an employer, billed at that actor's own price per person sent to it, found or not (0.03… |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-personal-email-to-company-resolver server?
com.mambabuilt/mcp-personal-email-to-company-resolver runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-personal-email-to-company-resolver. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-personal-email-to-company-resolver
claude mcp add com-mambabuilt-mcp-personal-email-to-company-res -- npx -y @mambalabsdev/mcp-personal-email-to-company-resolver
What is the com.mambabuilt/mcp-personal-email-to-company-resolver server?
com.mambabuilt/mcp-personal-email-to-company-resolver is listed in the public MCP registry as com.mambabuilt/mcp-personal-email-to-company-resolver. Find the likely employer behind a Gmail or other free mail signup, with a confidence. This page covers its npm package (@mambalabsdev/mcp-personal-email-to-company-resolver).
Is the com.mambabuilt/mcp-personal-email-to-company-resolver server safe to use?
com.mambabuilt/mcp-personal-email-to-company-resolver scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 com.mambabuilt/mcp-personal-email-to-company-resolver server expose?
com.mambabuilt/mcp-personal-email-to-company-resolver exposes 1 tool: resolve_personal_email_employer. Their descriptions and schemas cost roughly 424 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-personal-email-to-company-resolver server still maintained?
com.mambabuilt/mcp-personal-email-to-company-resolver is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-personal-email-to-company-resolver server under?
com.mambabuilt/mcp-personal-email-to-company-resolver declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.