Enrich Layer MCP Server
OfficialRelated Servers
Alternatives to Enrich Layer MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceProvides 19 B2B data enrichment tools for finding and validating emails, searching company profiles, analyzing job postings, discovering employee information, and researching advertising campaigns through the LeadMagic API.197 npm7MIT
- AlicenseCqualityDmaintenanceEnables access to LinkedIn data including profile enrichment, company information, job searches, post analytics, and social interactions through the LinkedIn Api8 API with comprehensive search and data retrieval capabilities.51MIT

Prospeo MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI tools to search and enrich B2B leads, including finding professional emails, company profiles, and filtering people and companies by various criteria.5283 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables agents to search and enrich B2B companies and people, find verified work emails and US phone numbers, search job postings, and consult live documentation, exposing one tool per API endpoint.1MIT

Scrupp MCP serverofficial
AlicenseAqualityAmaintenanceExport LinkedIn, Sales Navigator and Apollo searches, find decision makers, and find and verify work emails from any MCP client.1038 npmMIT- AlicenseNot gradedqualityDmaintenanceAccount-based marketing enrichment for AI agents. Enriches people and companies from email, LinkedIn URL, or domain with cited multi-source fields.13 npm1MIT
TDQS
Scored across 25 tools
Tool families are grouped by entity (company, person, school, job, credit), and each tool has a distinct input/output relationship. A few pairs like employee_list vs employee_search and company_lookup vs company_id_lookup could initially be confused, but their descriptions clarify different query inputs and result sets.
All tools share the enrich_ prefix and most follow an enrich_<entity>_<operation> pattern, making navigation predictable. Minor deviations like enrich_reverse_email, enrich_work_email, and enrich_disposable_email omit the person entity, but the intent remains clear.
The server covers multiple subdomains (companies, people, jobs, schools, credit) and nearly every tool has a distinct purpose. However, 25 tools is at the heavy end for an MCP server, making it feel more like a full API surface than a focused tool set.
Company, person, and job domains have strong lookup/search/profile coverage, including useful reverse and contact enrichment tools. The school domain is thinner: school_profile and student_list require a school URL, and there is no school lookup or search to discover that URL.