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. 93 installs a week from npm. Last commit 8 Sep 2026.

Resolves a company domain or name to its LinkedIn URL with confidence and firmographics.

Installs per day peak 31 · avg 16 · +23% w/w
a month agotoday
93
Installs / week
npm · @mambalabsdev/mcp-domain-to-linkedin-url-resolver
2
Stars
0 open issues
8 Sep 2026
Last commit
0 releases in 90 days
MIT
License
TypeScript

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 -- npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-domain-to-linkedin-url-resolver": {
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-domain-to-linkedin-url-resolver]
command = "npx"
args = ["-y", "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"]
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-domain-to-linkedin-url-resolver": {
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-domain-to-linkedin-url-resolver": {
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: APIFY_TOKEN (Apify API token from https://console.apify.com/account/integrations). The author declared them in the registry entry; get the values from the project itself.

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.

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

Resolve a company domain to its LinkedIn page with the exact follower count.

36 installs/wk local only
MCP Gtm Job Discovery
by mambabuilt

Find companies hiring for your role keywords, with firmographics and LinkedIn per posting.

90 installs/wk local only
MCP Youtube Channel Transcript Extractor
by mambabuilt

Resolve a company domain to its YouTube channel with subscriber count and metadata.

35 installs/wk local only
Anymail Finder
by anymailfinder

Find verified work emails from a name, company, role or LinkedIn URL, and verify emails you have.

24 installs/wk answering
MCP Meta Brand Presence Mapper
by mambabuilt

Resolve a company domain to Instagram, Threads and Facebook accounts and counts.

34 installs/wk local only
MCP Reddit Brand Presence Mapper
by mambabuilt

Resolve a company domain to its subreddit and sample public mentions of the brand.

36 installs/wk local only
MCP Company Social Presence Mapper
by mambabuilt

Map a company domain to its social media URLs and follower counts via Apify.

76 installs/wk local only

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 93 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 with the file path 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 93 times in the last week. Week over week that is +23%. 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 TypeScript 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.