Mcp Domain To Linkedin Url Resolver

com.mambabuilt由 mambabuilt.com 發布v1.3.1更新於 Nov 7, 2026

Resolves a company domain or name to its LinkedIn URL from search results, with confidence.

概覽

AI 產生的概覽

透過 Apify actor 將公司網域或名稱解析為 LinkedIn 公司頁面網址,並附上信心分數與社群連結。

可以做什麼
  • 將單一公司網域或名稱解析為 LinkedIn 公司頁面網址,附上高、中、低信心分數與解析方式
  • 一次呼叫解析多個純網域,每間公司回傳一列扁平 JSON 資料
  • 每列同時回傳 Facebook、Instagram、X、YouTube 等社群頁面連結
  • 可選擇從搜尋結果摘要讀取員工人數、產業、總部位置、追蹤人數與公司簡介等企業資訊
  • 可略過 7 天快取,強制重新解析
適用情境
適合需要為一批網域或公司名稱取得 LinkedIn 公司頁面網址的情境,例如補齊 CRM 或 Clay 增補資料中的連結缺口,或為外銷開發與 GTM 流程準備資料列。它是單一用途的查詢工具,並非通用搜尋服務。
執行需求
透過 npx 以 stdio 在本機執行,需要 Node.js 18 或更新版本。需要 Apify 帳號,並以 APIFY_TOKEN 環境變數提供 Apify API 權杖。解析在 Apify 上執行,需要網路連線。
安裝前請注意
APIFY_TOKEN 是付費服務的憑證,應妥善保密。費用依 Apify 事件計價:每次執行有啟動事件,每寫入一列資料另行收費,因此大量網域清單會產生費用;可用 max_charge_usd 限制單次執行花費。查詢內容與網域會傳送給 Apify 及公開搜尋引擎,執行失敗時會以錯誤形式回傳。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Domain To Linkedin Url Resolver,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Domain to LinkedIn URL Resolver MCP Server

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

[Domain To Linkedin Url Resolver MCP server]

An MCP server that resolves a company domain or name to its LinkedIn company URL. It wraps the Mamba Labs Domain to LinkedIn URL Resolver actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

What it does

Give it a company domain or a company name and it finds the matching LinkedIn company URL in public search results (it never requests a page on LinkedIn), with a confidence of high, medium, or low so you know how much to trust it, plus the company's Facebook, Instagram, X, and YouTube links, all in one flat row. Firmographics (employee count, industry, headquarters, follower count, description) are read from search result snippets when you set includeFirmographics to true; they are off by default and null when off or when no snippet states them. Pass domains to resolve a list in one call ready for Clay, a CRM, or an AI agent workflow. All of the resolution runs on Apify. This package is a thin client that calls 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": {    "mamba-linkedin-resolver": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-domain-to-linkedin-url-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 resolve_linkedin_url tool will be available.

Prerequisites

  • Node.js 18 or newer
  • An Apify account with an API token

Example prompts

  • "Find the LinkedIn page for stripe.com."
  • "What is the LinkedIn company URL for openai.com? Include the confidence score."
  • "Resolve the company named Figma to its LinkedIn URL and firmographics."
  • "Get the LinkedIn URL, employee count, and industry for datadoghq.com, with firmographics on."
  • "Resolve the LinkedIn pages for stripe.com, notion.so, and figma.com."

Inputs

  • company_domain (optional): the bare company domain, no https:// and no trailing slash. Example: stripe.com
  • company_name (optional): the company name.
  • domains (optional, array): a list of bare domains resolved in one run, one row per domain.
  • batchSize (optional, integer): how many domains from the list are resolved at once. 1 to 10. Default 2.
  • includeFirmographics (optional, boolean): also read employee_count_approx, industry, hq_location, follower_count, and company_description from search result snippets. No request is sent to LinkedIn. Default false. Those fields are null when it is off or when no snippet states them. The string forms "true" and "false" are accepted too.
  • skipCache (optional, boolean): ignore the 7 day cache and resolve again. Default false. The string forms are accepted too.

Provide at least one of company_domain, company_name, or domains. If a domain and a name are both given, the domain takes priority.

Output

The tool returns the actor's flat JSON row per company: company_domain, company_name, linkedin_company_url, linkedin_slug, resolution_method, confidence (high, medium, or low), facebook_url, instagram_url, twitter_url, youtube_url, the firmographic fields employee_count_approx, industry, hq_location, follower_count, and company_description (null unless includeFirmographics is true), slug_mismatch, run_date, degraded, and degradation_reason.

Example output

Run with includeFirmographics set to true.

json
{  "company_domain": "linear.app",  "company_name": "Linear",  "linkedin_company_url": "https://www.linkedin.com/company/linear-app",  "linkedin_slug": "linear-app",  "resolution_method": "google_search",  "confidence": "high",  "industry": "Software Development",  "employee_count_approx": "201",  "hq_location": "San Francisco, California, United States",  "run_date": "2026-05-28"}

Features

  • Public search results (Brave, then Bing) checked against the slug variants the domain implies. No request is sent to linkedin.com
  • Fixes the LinkedIn URL gaps in Clay native enrichment
  • Confidence scoring (high, medium, low) and resolution_method
  • Social links on every row; firmographics (employee count, industry, HQ) when includeFirmographics is true
  • One domain or a list per call

Pricing

Domain to LinkedIn URL 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.006 (FREE tier), down to $0.0051 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.

The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. A run that does not succeed comes back as an error with its run ID and status.

Full actor documentation

This server is a thin client and holds no resolution logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:

https://apify.com/mambalabs/domain-to-linkedin-url-resolver


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

來源:README.md,提交 ffc6d18

工具

1

resolve_linkedin_url

Resolve LinkedIn URL

Resolve a company domain or name, or a list of domains, to the LinkedIn company URL. Returns one flat, Clay-ready JSON row per company with the LinkedIn URL and slug, a confidence of high, medium, or low, the resolution method, and Facebook, Instagram, X, and YouTube links. The URL is read from public search results; no request is ever sent to LinkedIn. Firmographics (employee count, industry, headquarters, follower count, description) are read from search result snippets only when includeFirmographics is true; with it off, or when no snippet states them, those fields are null. Successful resolutions are cached for 7 days unless skipCache is true. Use it when you have a domain or a name and need the LinkedIn company page; it does not find people. Provide company_domain, company_name, or domains. 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.

輸入參數domainsbatchSizeskipCachecompany_namecompany_domainmax_charge_usdincludeFirmographics

版本歷史

6
  1. v1.3.1最新Nov 5, 2026
  2. v1.3.0Oct 16, 2026
  3. v1.2.2Oct 12, 2026
  4. v1.2.1Oct 6, 2026
  5. v1.2.0Oct 6, 2026
  6. v1.1.1Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分