Mcp Company Identity Resolver

com.mambabuiltPublished by mambabuilt.comv1.2.1Updated Nov 7, 2026

Resolve company name, domain, or LinkedIn into one canonical identity with confidence scores.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Resolves a company name, domain, or LinkedIn URL into one canonical company identity with confidence scores, via an Apify actor.

What you can do
  • Resolve a company name, domain, or LinkedIn URL into a canonical name, primary domain, and LinkedIn company URL, each with a 0-100 confidence score, an overall score, and a match method.
  • Cross-check supplied inputs, fill in missing ones, and flag conflicts instead of merging them.
  • Resolve batches of company names or domains in one run, one row per company, with a configurable batch size.
  • Force a fresh lookup that ignores the 7-day result cache.
  • Return flat JSON rows with echoed inputs, per-field confidence, a resolved flag, and run metadata.
When to use it
Useful when you need to normalize messy company identifiers for sales or go-to-market data work, confirm whether a domain and a LinkedIn slug refer to the same company, or enrich a list of names or domains with canonical identity fields.
Requirements
Runs locally over stdio via npx, so Node.js 18 or newer is needed. Requires an Apify account and an Apify API token supplied in the APIFY_TOKEN environment variable. Network access to Apify is required, and the client must be a desktop MCP client such as Claude Desktop.
Before you install
The APIFY_TOKEN secret is passed in the client config, so keep that config file private. Usage is billed per event on Apify: a start event per run plus a charge per dataset row, with an optional max_charge_usd cost cap. Company names, domains, and LinkedIn URLs are sent to Apify and its actor for processing.

Installation

In SourceWeft

  1. Open Mcp Company Identity Resolver in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Company Identity Resolver MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Company 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

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:

json
{  "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 of company_name, domain, or linkedin_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.

EventPriceFires when
apify-actor-start$0.00005Once 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 aboveOnce per row written to the dataset.
max_charge_usdnumberOptional 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.

ActorImmutable Actor ID
GTM Hiring Signal ScraperD7O1SA2EqwHGsGr1P
GTM Tech Stack Signal Enrichmentqyd7nNyqFPelQViBx
GTM Signals AggregatorxKdRfnfFNkdMpFuNs
Job Board Keyword Signal Scanner4DvqpvhMR74NLcDDY
Domain to LinkedIn URL Resolver3HtnSaqPHOg1Qg5gx
ICP Fit ScorerW161DT8W4kW55dMFh
Domain Deliverability Checker0tVgxI7A6o9jMlxmc
Company Firmographic EnricherYlUtLWjfPpqykmB8g
Company Social Presence Mapper4k6CCemkgBDz18m2h
Company Identity Resolverlr8fTRAmZCBZmuwwh
Company Change-Event FeedoX44rS0fkEJ3rXLWe
Funding & Press Signal ScannerFS13X6dhQVgX3XOM6

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Source: README.md at commit e197ac2

Tools

1

resolve_company_identity

Resolve Company Identity

Resolve any combination of company name, domain, or LinkedIn URL into one canonical company identity: the name, primary domain, and LinkedIn company URL, each with a 0-100 confidence score plus an overall score and a match method. 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. Login-free and public-data only. Takes one company or a list (company_names or domains), one row per company. Returns flat Clay-ready JSON. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

ParametersdomaindomainsbatchSizeskipCachecompany_namelinkedin_urlcompany_namesmax_charge_usd

Version history

5
  1. v1.2.1LatestNov 5, 2026
  2. v1.2.0Oct 16, 2026
  3. v1.1.1Oct 6, 2026
  4. v1.1.0Oct 6, 2026
  5. v1.0.1Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts