# com.mambabuilt/mcp-linkedin-company-presence-mapper (npm · @mambalabsdev/mcp-linkedin-company-presence-mapper) Resolve a company domain to its LinkedIn page with the exact follower count. - Trust score: 83/100 (high trust) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-21 ## Components - npm · `@mambalabsdev/mcp-linkedin-company-presence-mapper`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-company-presence-mapper/mambalabsdev-mcp-linkedin-company-presence-mapper.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-company-presence-mapper/mambalabsdev-mcp-linkedin-company-presence-mapper) ## Channel facts - Registry: `npm` - Package: `@mambalabsdev/mcp-linkedin-company-presence-mapper` - Version: `1.0.0` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-21. - **Supply Chain Security**: 98/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - 31 of 96 dependencies flagged as unhealthy. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 29 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 70/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 402 tokens (~402/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 93/100 - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the com.mambabuilt/mcp-linkedin-company-presence-mapper server? com.mambabuilt/mcp-linkedin-company-presence-mapper runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-linkedin-company-presence-mapper. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add com-mambabuilt-mcp-linkedin-company-presence-map -- npx -y @mambalabsdev/mcp-linkedin-company-presence-mapper ``` ### Cursor ```json { "mcpServers": { "com-mambabuilt-mcp-linkedin-company-presence-map": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper" ] } } } ``` ### VS Code ```json { "servers": { "com-mambabuilt-mcp-linkedin-company-presence-map": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper" ] } } } ``` ### Codex ```bash codex mcp add com-mambabuilt-mcp-linkedin-company-presence-map -- npx -y @mambalabsdev/mcp-linkedin-company-presence-mapper ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-mambabuilt-mcp-linkedin-company-presence-map": { "type": "local", "command": [ "npx", "-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-mambabuilt-mcp-linkedin-company-presence-map --command npx --arg -y --arg @mambalabsdev/mcp-linkedin-company-presence-mapper ``` ### Hermes ```yaml mcp_servers: com-mambabuilt-mcp-linkedin-company-presence-map: command: "npx" args: ["-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper"] ``` ### Netclaw ```json { "McpServers": { "com-mambabuilt-mcp-linkedin-company-presence-map": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper" ] } } } ``` ### Vellum ```bash assistant mcp add com-mambabuilt-mcp-linkedin-company-presence-map -t stdio -c npx -a -y @mambalabsdev/mcp-linkedin-company-presence-mapper ``` ### Other ```json { "mcpServers": { "com-mambabuilt-mcp-linkedin-company-presence-map": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-21 (score 83, +1) No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-19 (score 82, +1) No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-17 (score 81, +1) No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-15 (score 80, +1) No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-13 (score 79, +1) No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-10 (score 78, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-08 (score 77, +1) No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-06 (score 76, +1) No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (1) ### `map_linkedin_company_presence` (~402 tokens) Map LinkedIn Company Page Presence Resolve a company domain to its LinkedIn company page and return the EXACT follower count, plus the industry, declared company size band, headquarters, founded year and specialties that LinkedIn publishes on the public page. LinkedIn renders every digit, so unlike most social platforms these counts can be summed across a list. Everything comes from the logged out page: no login, no session cookie, no vendor. Employee lists, employee growth and post engagement are NOT reachable logged out and are not returned. A guessed slug that resolves to a different company is reported as identity_mismatch. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. Input parameters: - `company_domain` (string): Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch. - `company_name` (string): Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches. - `handle` (string): Optional. The company slug from linkedin.com/company/, for example shopify. Supplying it skips discovery and goes straight to the fetch. - `includeFirmographics` (boolean): When "true" (default) industry, company size band, headquarters, founded year and website are parsed off the page alongside the follower count. Set "false" for the URL and follower count only. Sent a… - `includeFollowerCounts` (boolean): When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and needs no proxy. Sent as a string for Clay compatibili… - `skipCache` (boolean): When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility. ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-company-presence-mapper/mambalabsdev-mcp-linkedin-company-presence-mapper#diagnostics ## Score history - 2026-09-21: 83 - 2026-09-20: 82 - 2026-09-19: 82 - 2026-09-18: 81 - 2026-09-17: 81 - 2026-09-16: 80 - 2026-09-15: 80 - 2026-09-14: 79 - 2026-09-13: 79 - 2026-09-12: 78 - 2026-09-11: 78 - 2026-09-10: 78 - 2026-09-09: 77 - 2026-09-08: 77 - 2026-09-07: 76 - 2026-09-06: 76 - 2026-09-05: 75 - 2026-09-04: 75 - 2026-09-03: 74 - 2026-09-02: 74 - 2026-09-01: 73 - 2026-08-31: 73 - 2026-08-30: 70 - 2026-08-29: 70 - 2026-08-28: 70 - 2026-08-27: 70 - 2026-08-26: 70 - 2026-08-25: 68 - 2026-08-24: 53 ## Common questions ### What is the com.mambabuilt/mcp-linkedin-company-presence-mapper server? com.mambabuilt/mcp-linkedin-company-presence-mapper is listed in the public MCP registry as com.mambabuilt/mcp-linkedin-company-presence-mapper. Resolve a company domain to its LinkedIn page with the exact follower count. This page covers its npm package (@mambalabsdev/mcp-linkedin-company-presence-mapper). ### Is the com.mambabuilt/mcp-linkedin-company-presence-mapper server safe to use? com.mambabuilt/mcp-linkedin-company-presence-mapper scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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-linkedin-company-presence-mapper server expose? com.mambabuilt/mcp-linkedin-company-presence-mapper exposes 1 tool: map_linkedin_company_presence. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded. ### Is the com.mambabuilt/mcp-linkedin-company-presence-mapper server still maintained? com.mambabuilt/mcp-linkedin-company-presence-mapper is still listed as active in the MCP registry. We last reached this channel on 21 September 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-linkedin-company-presence-mapper server under? com.mambabuilt/mcp-linkedin-company-presence-mapper declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-linkedin-company-presence-mapper - Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-linkedin-company-presence-mapper - Repository: https://github.com/mambalabsdev/mcp-linkedin-company-presence-mapper - Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-company-presence-mapper/mambalabsdev-mcp-linkedin-company-presence-mapper.xml - Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-company-presence-mapper/mambalabsdev-mcp-linkedin-company-presence-mapper.json - HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-company-presence-mapper/mambalabsdev-mcp-linkedin-company-presence-mapper