resolve_company_identityLABSCO SUMMARY
The identity step before any enrichment.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus a key — npx -y @mambalabsdev/mcp-company-identity-resolver, then supply credentials
USE CASES
01
Deduplicating a lead list
Resolve each row to a canonical domain first, then merge on that instead of on the company name someone typed.
02
Finding the domain behind a company name
Give it the name from a conference badge or an email signature and get the primary domain back with a score saying how confident the match is.
03
Checking whether two records are the same company
Pass the domain and the LinkedIn URL together: agreement comes back as one identity, disagreement comes back flagged rather than silently reconciled.
04
Filling the LinkedIn column on an outbound list
Start from the domain you already have and get the company page URL, with a per-field score you can use as a threshold for what to keep.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- npx on PATH
- Node.js 18 or later
- APIFY_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @mambalabsdev/mcp-company-identity-resolverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"company-identity-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-company-identity-resolver"
],
"env": {
"APIFY_TOKEN": "<YOUR_APIFY_TOKEN>"
}
}
}
}
