MCP Domain To Linkedin Url Resolver logo

MCP Domain To Linkedin Url Resolver

by mambalabsdev

Resolves company domains or names to LinkedIn URLs with confidence scores, social links, and optional firmographic data.

Install MCP Domain To Linkedin Url Resolver

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mambalabsdev-mcp-domain-to-linkedin-url-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

mambalabsdev/mcp-domain-to-linkedin-url-resolver connects MCP clients to an Apify-backed resolver for matching company domains or names with LinkedIn company URLs. Its `resolve_linkedin_url` tool returns a flat JSON row containing the URL, confidence level, resolution method, social links, and optional firmographics. It supports single lookups and domain lists, with optional caching controls and batch sizing. Use it for enrichment workflows involving Clay, CRMs, or agents that need public-search-based company identity resolution.

Use cases

  • Resolve company domains to LinkedIn URLs
  • Enrich company records with confidence scores
  • Process domain lists for Clay or CRM workflows
  • Retrieve optional company firmographics
  • Find social profiles alongside LinkedIn pages

Key features

  • Domain and company-name resolution
  • Confidence and resolution-method fields
  • Single or batch domain processing
  • Optional firmographic enrichment
  • Social profile URL output
  • Seven-day cache with bypass control

Tools1

What MCP Domain To Linkedin Url Resolver lets your agent do. Expand a tool for its parameters.

Verified live~375 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

22/23 checks healthy over the last 93d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @mambalabsdev/mcp-domain-to-linkedin-url-resolver (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Tools exposed1Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Domain To Linkedin Url Resolver works

What mambalabsdev/mcp-domain-to-linkedin-url-resolver does

mambalabsdev/mcp-domain-to-linkedin-url-resolver turns a company domain or name into a LinkedIn company URL. Results include the matched company identity, LinkedIn slug, resolution method, and a confidence value of high, medium, or low. Each row can also include Facebook, Instagram, X, and YouTube URLs.

The response is flattened for downstream enrichment workflows. Optional firmographic fields include approximate employee count, industry, headquarters, follower count, and company description. These fields are populated from search-result snippets only when firmographic enrichment is enabled.

How it works

The package starts the Mamba Labs Domain to LinkedIn URL Resolver actor on Apify and waits for the run to finish. Resolution uses public search results and checks slug variants implied by the supplied company identity. The resolver does not request pages from LinkedIn itself.

Supply at least one of company_domain, company_name, or domains. If both a domain and name are supplied, the domain takes precedence. The domains option accepts multiple bare domains and produces one output row per domain. A seven-day cache is used by default; skipCache forces a new resolution.

Setup and configuration

The runtime requires Node.js 18 or newer, an Apify account, and an Apify API token. Set the token as APIFY_TOKEN in the MCP client's environment. For Claude Desktop, the package can be launched with npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver.

Relevant inputs include:

  • company_domain: a bare domain such as stripe.com, without a protocol or trailing slash.
  • company_name: the company name to resolve.
  • domains: an array of bare domains for multi-domain runs.
  • batchSize: number of domains processed together, from 1 to 10; the default is 2.
  • includeFirmographics: enables firmographic fields; the default is false.
  • skipCache: bypasses the seven-day cache; the default is false.

Tools and capabilities

The server exposes resolve_linkedin_url. It returns fields such as linkedin_company_url, linkedin_slug, confidence, resolution_method, social URLs, firmographic values, run_date, and degradation status fields. The operation is read-only.

A single call can resolve one company or a list of domains. The flat output can be passed to Clay, a CRM, or another agent workflow without reshaping nested records.

Limitations and notes

Every resolution runs through Apify and consumes Apify usage. Charges include actor-start and dataset-item events; the underlying actor also supports an optional USD maximum charge for a run. Firmographic values are null when enrichment is disabled or when search snippets do not contain the requested data.

A failed Apify run is returned as an error with its run ID and status. The server is a thin client, so the resolution logic and actor-level behavior are handled by the Apify actor rather than locally.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Domain To Linkedin Url Resolver

mambalabsdev/mcp-domain-to-linkedin-url-resolver is an MCP server that connects MCP clients to an Apify-backed public-search resolver. Its main tool, `resolve_linkedin_url`, accepts a company domain, name, or domain list and returns LinkedIn URLs with confidence scores, social links, and optional firmographic metadata.

Install it by configuring your MCP client to run `npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver` and providing `APIFY_TOKEN`. Node.js 18 or newer and an Apify account are required. The package can be added to Claude Desktop's MCP server configuration.

It accepts `company_domain`, `company_name`, or `domains`; at least one is required. Optional inputs include `batchSize`, `includeFirmographics`, and `skipCache`. Domains should be bare values such as `stripe.com`, without `https://` or a trailing slash.

No, it resolves companies from public search results and does not request pages on LinkedIn. Optional firmographics are read from search-result snippets. Resolution is performed by the Mamba Labs actor running on Apify.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Domain To Linkedin Url Resolver AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mambalabsdev-mcp-domain-to-linkedin-url-resolver?style=directory)](https://allmcps.com/mcp/mambalabsdev-mcp-domain-to-linkedin-url-resolver)
HTML Embed
<a href="https://allmcps.com/mcp/mambalabsdev-mcp-domain-to-linkedin-url-resolver"><img src="https://allmcps.com/api/badge/mambalabsdev-mcp-domain-to-linkedin-url-resolver?style=directory" alt="MCP Domain To Linkedin Url Resolver on AllMCPs" /></a>