mcpbeat Sign in

MCP Domain To Linkedin URL Resolver MCP Server

local only

MCP Domain To Linkedin URL Resolver runs on your own machine — the client starts it, so there is no endpoint to ping. 109 installs a week from npm. Last commit 20 Oct 2026.

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

Installs per day peak 187 · avg 23 · -54% w/w
a month agotoday
109
Installs / week
npm · @mambalabsdev/mcp-domain-to-linkedin-url-resolver
2
Stars
0 open issues
20 Oct 2026
Last commit
6 releases in 90 days
MIT
License
JavaScript

Nothing serious here today

Today is the operative word: we check MCP Domain To Linkedin URL Resolver every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add mcp-domain-to-linkedin-url-resolver -e 'APIFY_TOKEN=<APIFY_TOKEN>' -- npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-domain-to-linkedin-url-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ],
      "env": {
        "APIFY_TOKEN": "<APIFY_TOKEN>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-domain-to-linkedin-url-resolver]
command = "npx"
args = ["-y", "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"]
env = { APIFY_TOKEN = "<APIFY_TOKEN>" }
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-domain-to-linkedin-url-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ],
      "env": {
        "APIFY_TOKEN": "<APIFY_TOKEN>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp-domain-to-linkedin-url-resolver": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ],
      "env": {
        "APIFY_TOKEN": "<APIFY_TOKEN>"
      }
    }
  }
}

Put your own value in place of <APIFY_TOKEN> (Apify API token from https://console.apify.com/account/integrations). The author’s registry entry marks it as required.

Alternatives to MCP Domain To Linkedin URL Resolver

same job, measured the same way
MCP Company Identity Resolver
by mambabuilt

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

90 installs/wk local only
MCP Person Linkedin URL Resolver
by mambabuilt

Find a person's LinkedIn profile URL from name and company, with a match confidence.

165 installs/wk local only
MCP Linkedin Company Presence Mapper
by mambabuilt

Free. Resolve a company domain to its verified LinkedIn page, name and tagline.

97 installs/wk local only
MCP Company Headcount Estimator
by mambabuilt

Employee count band for a company domain, with source and confidence. No LinkedIn login.

164 installs/wk local only
LinkedIn Company Data
by saulius876-lgtm

LinkedIn company size, industry, website, HQ, followers, posts from links, domains or names.

answering
MCP Linkedin Jobs Feed
by mambabuilt

LinkedIn job search results with the employer website domain on every row. No login.

local only
Namewhere: Company Name to Domain & Website Finder
by cybermax-tools

Namewhere: company name to official website domain, confidence, evidence, socials.

answering
Namewhere: Company Name to Domain & Website Finder
by shawmena-dotcom

Namewhere: company name to official website domain, confidence, evidence, socials.

answering

MCP Domain To Linkedin URL Resolver — questions

Answers built from our own checks of this server.

Why is there no uptime for MCP Domain To Linkedin URL Resolver?
MCP Domain To Linkedin URL Resolver runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @mambalabsdev/mcp-domain-to-linkedin-url-resolver was installed 109 times last week.
How do I connect MCP Domain To Linkedin URL Resolver?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @mambalabsdev/mcp-domain-to-linkedin-url-resolver straight from npm; nothing to host, nothing to sign up for.
How many people use MCP Domain To Linkedin URL Resolver?
The npm package @mambalabsdev/mcp-domain-to-linkedin-url-resolver was installed 109 times in the last week. Week over week that is -54%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is MCP Domain To Linkedin URL Resolver open source?
Yes — it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.