mcp-company-identity-resolver
LocalAbout mcp-company-identity-resolver
An MCP server that wraps Mamba Labs’ Company Identity Resolver on Apify. It resolves company names, domains or LinkedIn URLs into a canonical identity with field-level and overall confidence scores, and flags conflicting inputs.
Key features
- 01Resolve names, domains and LinkedIn URLs
- 02Return canonical company identity fields
- 03Score confidence per field and overall
- 04Flag conflicting identity inputs
- 05Resolve multiple companies in batches
Use cases
- 01Normalize company records from mixed identifiers
- 02Check whether a domain and LinkedIn URL match
- 03Enrich a batch of company names with domains
MCP support
Exposes the `resolve_company_identity` tool to MCP clients. It routes calls to the Apify actor and returns flat JSON rows, one per resolved company.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @mambalabsdev/mcp-company-identity-resolverAPIFY_TOKENSecretApify API token from https://console.apify.com/account/integrationsLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
1Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| domain | string | No | Bare company domain, e.g. stripe.com. The strongest canonical key when provided. |
| domains | array | No | A list of bare company domains to resolve in one run, one row per domain. Use instead of domain for a batch. |
| batchSize | integer | No | How many companies from the lists are resolved at once. 1 to 10. Default: 2. |
| skipCache | boolean | No | Force a fresh resolution and ignore the 7 day result cache. |
| company_name | string | No | Company name, e.g. Stripe. Provide at least one of company_name, domain, or linkedin_url. |
| linkedin_url | string | No | LinkedIn company URL (https://www.linkedin.com/company/stripe) or bare slug (stripe). |
| company_names | array | No | A list of company names to resolve in one run, one row per company. Use instead of company_name for a batch. |
Details
From the project READMECompany Identity Resolver MCP Server
An MCP server that exposes the Mamba Labs Company Identity Resolver as a single tool. Install one package and give your MCP client a way to turn any combination of company name, domain, or LinkedIn URL into one canonical company identity tuple with confidence scores, wrapping the Mamba Labs actor on Apify and returning Clay-ready flat JSON.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Tool and inputs
- Pricing
- Full actor documentation
- Mamba Labs GTM Suite
- License
What it does
This server gives an AI client one tool:
resolve_company_identity: resolve any combination of company name, domain, or LinkedIn URL into the canonical name, primary domain, and LinkedIn company URL, each with a 0-100 confidence score plus an overall score and a match method. It cross-checks the inputs you give it, resolves the ones you do not, and flags conflicts (a domain and a LinkedIn slug that disagree) instead of merging them.
All of the work runs on Apify. This package is a thin client that routes the tool call to the actor and hands back the result.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
{
"mcpServers": {
"company-identity-resolver": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-company-identity-resolver"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}
Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The tool will be available.
Prerequisites
- Node.js 18 or newer
- An Apify account with an API token
Example prompts
- "Resolve the canonical identity for the company 'Stripe' and give me its domain and LinkedIn URL with confidence scores."
- "I have the domain notion.so; what is the canonical company name and LinkedIn URL?"
- "Do domain stripe.com and LinkedIn slug notion refer to the same company?"
- "Resolve the company at linkedin.com/company/gitlab-com into its domain and name."
Tool and inputs
resolve_company_identity:
company_name(string): company name, e.g. Stripe. Provide at least one ofcompany_name,domain, orlinkedin_url.domain(string): bare company domain, e.g. stripe.com. The strongest canonical key when provided.linkedin_url(string): LinkedIn company URL (https://www.linkedin.com/company/stripe) or bare slug (stripe).company_names(array of strings): a list of company names resolved in one run, one row per company.domains(array of strings): a list of bare domains resolved in one run, one row per domain.batchSize(integer): how many companies from the lists are resolved at once.skipCache(boolean): force a fresh resolution and ignore the 7 day result cache.
Provide at least one of company_name, domain, linkedin_url, company_names, or domains.
The output is one flat row: the echoed inputs, the canonical name, domain, and linkedin_url, the overall confidence_score, the match_method (exact_domain, search_resolved, linkedin_pattern, jsonld, conflict, or unresolved), the per-field domain_confidence, linkedin_confidence, and name_confidence, a resolved boolean, and the run fields degraded, degradation_reason, and run_date. A list input returns one such row per company.
The tool starts the actor run and polls it to a finished status, so a long batch is not cut off at 300 seconds. A run that does not succeed comes back as an error with its run ID and status.
Pricing
Company Identity Resolver is pay per event on Apify.
| Event | Price | Fires when |
|---|---|---|
apify-actor-start | $0.00005 | Once per run, on start, one event per GB of memory (minimum one). Apify's start event. |
apify-default-dataset-item | $0.007 (FREE tier), down to $0.00595 on GOLD and above | Once per row written to the dataset. |
max_charge_usd | number | Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. |
Full actor documentation
For the complete input and output reference, pricing, and run history, see the Company Identity Resolver actor on the Apify Store:
https://apify.com/mambalabs/company-identity-resolver
The wrapper calls the actor by its immutable ID lr8fTRAmZCBZmuwwh, so a Store rename never breaks it.
Mamba Labs GTM Suite
This server is part of the Mamba Labs GTM Suite, a fleet of twelve specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.
| Actor | Immutable Actor ID |
|---|---|
| GTM Hiring Signal Scraper | D7O1SA2EqwHGsGr1P |
| GTM Tech Stack Signal Enrichment | qyd7nNyqFPelQViBx |
| GTM Signals Aggregator | xKdRfnfFNkdMpFuNs |
| Job Board Keyword Signal Scanner | 4DvqpvhMR74NLcDDY |
| Domain to LinkedIn URL Resolver | 3HtnSaqPHOg1Qg5gx |
| ICP Fit Scorer | W161DT8W4kW55dMFh |
| Domain Deliverability Checker | 0tVgxI7A6o9jMlxmc |
| Company Firmographic Enricher | YlUtLWjfPpqykmB8g |
| Company Social Presence Mapper | 4k6CCemkgBDz18m2h |
| Company Identity Resolver | lr8fTRAmZCBZmuwwh |
| Company Change-Event Feed | oX44rS0fkEJ3rXLWe |
| Funding & Press Signal Scanner | FS13X6dhQVgX3XOM6 |
Built by Mamba Labs | npm | Apify Store
License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.