Personal Email to Company Resolver MCP Server
Related Servers
Alternatives to Personal Email to Company Resolver MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables users to look up a person's public GitHub, Bluesky, personal site, Substack, and X profiles from their full name and company domain, with status and confidence per platform and no emails or phone numbers.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to verify email addresses through a multi-signal probabilistic pipeline, returning confidence scores and honest statuses (safe/risky/invalid/unknown) with evidence.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables free breach-exposure lookup by email address, revealing data breaches, exposed data classes, and risk scores without requiring an API key.184 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search a global professional database in plain English, reveal full profiles, and fetch verified work emails, email verification, reverse email lookup, and LinkedIn and company lookups. Searches are free, while most lookups cost credits that are refunded automatically when nothing is found.MIT
- AlicenseAqualityBmaintenanceEnables users to estimate employee count bands for company domains by aggregating LinkedIn company size from Google results, Wikidata, and homepage declarations. Returns source, confidence score, and optional GitHub member and open-job context.1333 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnriches person profiles from email addresses, returning full name, job title, company, social links, and location. Works as a drop-in replacement for Apollo person enrichment at lower cost.MIT
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.