fairquery-contact-enricher
OfficialRelated Servers
Alternatives to fairquery-contact-enricher
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnriches domains into full company profiles with firmographics and buying signals.-
- AlicenseAqualityAmaintenanceEnables enriching company domains into structured firmographics including employee band, industry, HQ, founded year, revenue estimate, logo, and description, with source provenance and data completeness scoring.177 npm1MIT
- AlicenseAqualityBmaintenanceDomain and company intelligence for AI agents. Enables vetting companies, qualifying leads, and mapping targets from free public data without API keys.62 npm1MIT
- AlicenseAqualityDmaintenanceEnables scraping of emails, phone numbers, and social profile links from website domains. Supports batch processing of up to 20 domains and can find company websites by keyword/company name.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables targeted company discovery, real-time DNS MX deliverability diagnostics, and clean web Markdown extraction for AI agents.MIT
- AlicenseNot gradedqualityFmaintenanceProvides domain and brand intelligence for AI agents, including company enrichment, tech stack detection, and brand research from free public sources with an on-demand cache.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: normalize_domains cleans and previews input locally for free, while enrich_domains performs the paid network enrichment. The descriptions explicitly state when to use each and when not to use them, eliminating overlap.
Both tool names follow the same predictable verb_noun snake_case pattern: normalize_domains and enrich_domains. The names clearly indicate the action and target resource.
A two-tool surface is thin but focused for a contact-enrichment server. The prep tool is useful, though the set could benefit from at least one additional operation for batch handling or cost estimation.
The core workflow—cleaning domains and enriching them with contact data—is covered well. Minor gaps remain around large-batch/async processing and explicit paid-cost preview, which agents may need for bigger lead lists.