Enterprise DNA
M MCP Servers Developer low

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

by Various

MCP server for Domain to LinkedIn URL Resolver. Resolves a company domain or name to its LinkedIn company URL with confidence scoring and firmographics via Apify. Clay-ready output

M

MCP

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

Added 11 June 2026

Overview

An MCP server that resolves a company domain or name to its LinkedIn company URL. It uses Apify to return the URL with a confidence score and firmographic data, outputting results in a Clay-ready format.

Best for

Best for
Developers building automated lead enrichment or sales prospecting pipelines that need LinkedIn company URLs from domains.

Use cases

  • Enrich lead lists with LinkedIn company URLs from domains
  • Automate company research for sales prospecting workflows
  • Integrate with Clay or other tools for data enrichment pipelines

Notes

An MCP server that resolves a company domain or name to its LinkedIn company URL. It uses Apify to return the URL with a confidence score and firmographic data, outputting results in a Clay-ready format.

1 stars on GitHub. Last updated 2026-06-09. Licensed MIT.

Use cases

  • Enrich lead lists with LinkedIn company URLs from domains
  • Automate company research for sales prospecting workflows
  • Integrate with Clay or other tools for data enrichment pipelines

Pros

  • Provides confidence scoring for each resolved URL
  • Returns firmographic data alongside the LinkedIn link
  • Outputs in a format compatible with Clay for further processing

Cons

  • Requires an Apify account and API key to function
  • Limited to 1 star on GitHub, indicating minimal community adoption
  • Dependency on external Apify service adds latency and cost

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Provides confidence scoring for each resolved URL
  • Returns firmographic data alongside the LinkedIn link
  • Outputs in a format compatible with Clay for further processing

Cons

  • Requires an Apify account and API key to function
  • Limited to 1 star on GitHub, indicating minimal community adoption
  • Dependency on external Apify service adds latency and cost

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.