com.mambabuilt/mcp-domain-to-linkedin-url-resolver
NPM · @MAMBALABSDEV/MCP-DOMAIN-TO-LINKEDIN-URL-RESOLVER
Resolves a company domain or name to its LinkedIn URL from search results, with confidence.
Available components
Last scanned (1 hour ago)
Scores higher than 30% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security13
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 548 tokens (~548/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 1.3.0 → 1.3.1 functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Schema quality: 495 → 548 ▼ functional
- Package version: 1.2.2 → 1.3.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@mambalabsdev/mcp-domain-to-linkedin-url-resolver@1.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
resolve_linkedin_url Resolve LinkedIn URL ~548
Resolve a company domain or name, or a list of domains, to the LinkedIn company URL. Returns one flat, Clay-ready JSON row per company with the LinkedIn URL and slug, a confidence of high, medium, or low, the resolution method, and Facebook, Instagram, X, and YouTube links. The URL is read from public search results; no request is ever sent to LinkedIn. Firmographics (employee count, industry, headquarters, follower count, description) are read from search result snippets only when includeFirmographics is true; with it off, or when no snippet states them, those fields are null. Successful resolutions are cached for 7 days unless skipCache is true. Use it when you have a domain or a name and need the LinkedIn company page; it does not find people. Provide company_domain, company_name, or domains. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | integer | – | How many domains from the list are resolved at once. 1 to 10. Default: 2. |
| company_domain | string | – | Bare company domain without https:// and without a trailing slash. Example: stripe.com. Required if company_name and domains are not provided. |
| company_name | string | – | Company name. Required if company_domain and domains are not provided. |
| domains | array | – | A list of bare company domains to resolve in one run, one row per domain. Example: ["stripe.com", "datadoghq.com"]. |
| includeFirmographics | – | – | When true, also reads firmographics from search result snippets about the LinkedIn company page: follower_count and company_description for most established companies, and employee_count_approx, indu… |
| max_charge_usd | number | – | Optional. The run stops before the next result that would take this run's charges over this amount, and keeps every result already charged. Leave empty to rely only on the maximum cost per run you se… |
| skipCache | – | – | When false, the default, a successful resolution is cached for 7 days and reused. Set true to force a fresh resolution. Accepts true or false, or the strings "true" and "false". Default: false. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-domain-to-linkedin-url-resolver server?
com.mambabuilt/mcp-domain-to-linkedin-url-resolver runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-domain-to-linkedin-url-resolver
claude mcp add com-mambabuilt-mcp-domain-to-linkedin-url-resolv -- npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver
What is the com.mambabuilt/mcp-domain-to-linkedin-url-resolver server?
com.mambabuilt/mcp-domain-to-linkedin-url-resolver is listed in the public MCP registry as com.mambabuilt/mcp-domain-to-linkedin-url-resolver. Resolves a company domain or name to its LinkedIn URL from search results, with confidence. This page covers its npm package (@mambalabsdev/mcp-domain-to-linkedin-url-resolver).
Is the com.mambabuilt/mcp-domain-to-linkedin-url-resolver server safe to use?
com.mambabuilt/mcp-domain-to-linkedin-url-resolver scores 58 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-domain-to-linkedin-url-resolver server expose?
com.mambabuilt/mcp-domain-to-linkedin-url-resolver exposes 1 tool: resolve_linkedin_url. Their descriptions and schemas cost roughly 548 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-domain-to-linkedin-url-resolver server still maintained?
com.mambabuilt/mcp-domain-to-linkedin-url-resolver is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-domain-to-linkedin-url-resolver server under?
com.mambabuilt/mcp-domain-to-linkedin-url-resolver declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.