Lead lists carry a name in one column, a domain in another and a LinkedIn URL somewhere else, and the expensive mistake is treating three spellings as three companies. This collapses them into one tuple and scores how sure it is — and when two inputs genuinely disagree it says so instead of quietly picking a winner.
A single-tool server in front of a Mamba Labs actor hosted on Apify. You give it whatever fragment of a company you have; it returns the canonical name, the primary domain and the LinkedIn company URL as one flat row.
- Any one of company name, domain or LinkedIn URL resolved into all three
- A confidence score per field and an overall score, plus the match method that produced them — exact domain, search, LinkedIn pattern, page metadata
- Conflicts flagged rather than merged: a domain and a LinkedIn slug that point at different companies come back marked as a conflict
- Cross-checking of the fields you do supply, not just filling in the ones you left out
- Flat JSON, shaped to drop into a spreadsheet column or an enrichment step
- A cached result by default, with a way to force a fresh resolution
Node, and an Apify account with an API token. The resolution itself runs as an actor on Apify under your account, and that actor's page carries its pricing and run history.
One command plus a key — npx -y @mambalabsdev/mcp-company-identity-resolver, then supply credentials