Company Enrichment MCP
Related Servers
Alternatives to Company Enrichment MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables agents to enrich domains into public business contact data, including MX/disposable-validated role emails, phones, social profiles, company names, and addresses, while respecting robots.txt; also normalizes URLs and emails into unique domains locally.3MIT
- AlicenseAqualityBmaintenanceDomain and company intelligence for AI agents. Enables vetting companies, qualifying leads, and mapping targets from free public data without API keys.64 npm1MIT
- 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.182 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnriches domains into full company profiles with firmographics and buying signals.-
- AlicenseNot gradedqualityBmaintenanceEnriches company data from a domain name, providing firmographics, socials, tech stack, and contact info via a pay-per-call x402 micropayment API.2MIT
- AlicenseAqualityCmaintenanceEnables enrichment of company domains with verified firmographic signals including tech stack, hiring activity, email infrastructure, and SOC 2 compliance, returning compact typed JSON for AI agents.38 npmMIT
TDQS
Scored across 4 tools
Each tool has a distinct action (probe hiring, describe schema, full enrich, grade email domain), and descriptions explicitly frame the lighter tools as cheap pre-checks versus the full enrich_company crawl. The only residual ambiguity is that company_hiring_signal and check_email_domain surface data already contained inside enrich_company's output, so an agent must judge when the lite path is worth it.
Three of four tools use a clean verb_noun snake_case pattern (list_capabilities, enrich_company, check_email_domain). company_hiring_signal breaks the pattern as a noun phrase, a minor deviation in an otherwise predictable scheme.
Four tools is small but well matched to a focused enrichment server: one meta/help tool, one heavy enrichment call, and two cheap probes. It sits at the lean edge of the 3-15 range, with the two probe tools arguably being extractable features of enrich_company rather than independent capabilities.
The surface covers the core enrichment lifecycle well: schema discovery, full domain-based enrichment with contacts/tech/hiring, plus targeted hiring and email-deliverability probes. Gaps are minor, e.g. no explicit bulk/batch status retrieval or follow-up lookup by a previously returned canonical domain, but agents can work around these by re-calling enrich_company.