1 findingStatic scanned
Scans a company's job board for sales, marketing and revenue operations hiring.
478 installs/moMIT
MCP Domain To Linkedin Url Resolver
mambalabsdev · MCP server
Resolves a company domain or company name to its LinkedIn company URL and returns a flat row ready for Clay, a CRM or an AI agent workflow. Each match carries a confidence rating of high, medium or low, and optional firmographics such as employee count, industry and headquarters. It calls an actor on Apify, so it needs an Apify account and API token, and Apify charges per event.
Written by ooruby from the README of @mambalabsdev/mcp-domain-to-linkedin-url-resolver 1.2.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Gives each account in a list its LinkedIn company URL and social links, with a rating of how sure the match is.
What you could do with it
- Find the LinkedIn page for a company domain and see how confident the match is.
- Resolve a whole list of company domains in one call and get one row for each.
- Turn on firmographics to get employee count, industry and headquarters with the LinkedIn URL.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Data handling disclosed
- finding
- no statement of what it reads, writes or sends (README.md)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
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.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 1.2.1, the file with digest sha512-Em1LvrB4nd1GSCAy/+KWuA037BORwcJ3wRjBYK+GOpNORk6DjL9ME9mChNZsRqN9bZsaQui84Ciy5dsoa6zCMw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"mcp-domain-to-linkedin-url-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-domain-to-linkedin-url-resolver@1.2.1"
]
}
}
}Or run it directly.
npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver@1.2.1Pinned to 1.2.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @mambalabsdev/mcp-domain-to-linkedin-url-resolver
- Version read
- 1.2.1
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/mambalabsdev-mcp-domain-to-linkedin-url-resolver)About this listing
- Kind
- MCP server
- Category
- Sales & CRM
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-06
More from mambalabsdev
See the storefrontSimilar MCP servers
All MCP serversClean scanStatic scanned
Lets your agent work with your Salesforce orgs, from Aura to LWC migration to code analysis.
171k installs/moApache-2.0
Clean scanStatic scanned
Lets your agent search and update HubSpot CRM records and associations, and add notes and tasks.
73.9k installs/moMIT
Clean scanStatic scanned
Lets your agent manage members, posts, leads, reviews and pages on a Brilliant Directories site.
26.4k installs/moMIT
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.