MCP Tools Directory
← Browse integrations

Developer tools

com.mambabuilt/mcp-domain-to-linkedin-url-resolver

Free account · sign-in required

Contact com.mambabuilt/mcp-domain-to-linkedin-url-resolver

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

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

Transport
stdio
Authentication
api-key
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
1.1.1
Package
@mambalabsdev/mcp-domain-to-linkedin-url-resolver
Last compatibility test
Not independently tested

Connect your agent

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

Publisher README and package manifest reviewed. Returned identity matches and confidence remain publisher-service output, not independent company verification.

Capabilities: Resolve company domains to LinkedIn URLs, Return confidence and resolution method, Return documented company firmographics

Connected profiles

Additional details

Registry identifier

com.mambabuilt/mcp-domain-to-linkedin-url-resolver

Source ↗ · Checked 2026-09-17
Published version

1.1.1

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Required configuration names

APIFY_TOKEN

Source ↗ · Checked 2026-09-17
Source artifact

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

Source ↗ · Checked 2026-09-19
Source manifest version

1.1.1

Source ↗ · Checked 2026-09-19
Unattended configuration

The package is documented as a thin client that calls an Apify actor and returns its result. It was not installed or executed.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

An Apify account and API token are required and configured through APIFY_TOKEN.

Source ↗ · Checked 2026-09-19
Connection configuration

The reviewed client configuration launches the npm package with npx over the existing stdio connection.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19