Skip to main content
Glama
mambalabsdev

mcp-domain-to-linkedin-url-resolver

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Domain to LinkedIn URL Resolver MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

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

Related MCP server: Company Firmographic Enricher MCP Server

What it does

Give it a company domain or a company name and it finds the matching LinkedIn company page, with a confidence score so you know how much to trust it. You also get firmographics such as employee count, industry, and headquarters, plus social links, all in one flat row 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:

{
  "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."

Inputs

  • company_domain (optional): the bare company domain, no https:// and no trailing slash. Example: stripe.com

  • company_name (optional): the company name.

Provide at least one of the two. If both are given, the domain takes priority.

Output

The tool returns the actor's flat JSON row, including the resolved LinkedIn company URL, a confidence score, firmographics such as employee count, industry, and headquarters, and social links. See the Apify Store page for the full output schema.

Example output

{
  "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

  • Google search plus URL pattern matching for high accuracy

  • Fixes the LinkedIn URL gaps in Clay native enrichment

  • Confidence scoring (high, medium, low) and resolution_method

  • Firmographics (employee count, industry, HQ) plus social links

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.

Actor

Immutable Actor ID

GTM Hiring Signal Scraper

D7O1SA2EqwHGsGr1P

GTM Tech Stack Signal Enrichment

qyd7nNyqFPelQViBx

GTM Signals Aggregator

xKdRfnfFNkdMpFuNs

Job Board Keyword Signal Scanner

4DvqpvhMR74NLcDDY

Domain to LinkedIn URL Resolver

3HtnSaqPHOg1Qg5gx

ICP Fit Scorer

W161DT8W4kW55dMFh

Domain Deliverability Checker

0tVgxI7A6o9jMlxmc

Company Firmographic Enricher

YlUtLWjfPpqykmB8g

Company Social Presence Mapper

4k6CCemkgBDz18m2h

Company Identity Resolver

lr8fTRAmZCBZmuwwh

Company Change-Event Feed

oX44rS0fkEJ3rXLWe

Funding & Press Signal Scanner

FS13X6dhQVgX3XOM6

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Available Tools

1 tool
resolve_linkedin_urlResolve LinkedIn URLA
Read-onlyIdempotent

Resolve a company domain or name to its LinkedIn company URL. Returns the LinkedIn URL with a confidence score, plus firmographics such as employee count, industry, and headquarters, and social links, as a flat, Clay-ready JSON row. Provide at least one of company_domain or company_name. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

ParametersJSON Schema
NameRequiredDescriptionDefault
company_domainNoBare company domain without https:// and without a trailing slash. Example: stripe.com. Required if company_name is not provided.
company_nameNoCompany name. Required if company_domain is not provided.

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context about requiring APIFY_TOKEN and consuming credits, which is valuable beyond annotations. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, efficiently conveying purpose, inputs, outputs, and constraints. No filler or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite lacking an output schema, the description fully specifies the return content (firmographics, confidence score, social links) and format (flat, Clay-ready JSON row). All relevant aspects are covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters. The description further clarifies that company_domain should be 'bare' without protocol or trailing slash, providing an example. This adds meaningful detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool resolves a company domain or name to its LinkedIn URL and lists the returned data (confidence score, firmographics, social links). It provides a specific verb ('resolve') and resource ('LinkedIn URL'), making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states the input requirement ('provide at least one of company_domain or company_name') and notes prerequisites (APIFY_TOKEN, credit consumption). While it does not mention alternatives, no siblings exist, so this is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.3
    • First observedresolve_linkedin_url
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no risk of ambiguity between tools. The single tool has a distinct and clear purpose.

Naming Consistency5/5

The single tool name 'resolve_linkedin_url' follows a clear verb_noun pattern, consistent with best practices.

Tool Count3/5

One tool is at the lower end of the range. While it serves a specific resolver function, the surface is minimal and might feel thin for broader use cases.

Completeness5/5

For the stated purpose of resolving a domain or name to a LinkedIn URL with firmographics, the single tool fully covers the intended operation with no obvious gaps.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources

Related MCP Connectors

Related MCP Servers

  • Company Firmographic Enricher

    mambalabsdev
    A
    license
    A
    quality
    A
    maintenance
    Enables enriching company domains into structured firmographics including employee band, industry, HQ, founded year, revenue estimate, logo, and description, with source provenance and data completeness scoring.
    1
    55 npm
    1
    MIT

  • Company Identity Resolver MCP

    mambalabsdev
    A
    license
    A
    quality
    A
    maintenance
    Resolves any combination of company name, domain, or LinkedIn URL into the canonical company identity (name, domain, LinkedIn URL) with confidence scores and match method.
    1
    55 npm
    MIT

  • LinkedIn Company API MCP

    johnisanerd
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to extract structured firmographic data from public LinkedIn company URLs, returning fields like name, industry, size, and headquarters.
    -