Personal Email to Company Resolver MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_personal_email_employerA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. Its purpose (resolve the employer behind a personal email address) is stated explicitly and unambiguously.
The single name resolve_personal_email_employer is descriptive snake_case with a clear verb_noun_qualifier structure. With only one tool there is no convention clash, and the name reads predictably.
A single-purpose resolver plausibly needs only one operation, and the tool accepts multiple addresses per call, so the count is not wrong. However, one tool is a thin surface for a billed, asynchronous Apify actor, leaving no companion operation for run inspection or cost checks.
The tool covers the full resolution lifecycle for its narrow domain: multiple input addresses, rich per-row output (name, employer, domain, source, confidence, match_status, LinkedIn URL, evidence), and documented failure statuses. The main gap is that failed runs only return a run ID with no tool to retrieve that run's results or status, which is a dead end for recovery.