com.mambabuilt/mcp-linkedin-post-engager-capture
NPM · @MAMBALABSDEV/MCP-LINKEDIN-POST-ENGAGER-CAPTURE
Collect the LinkedIn posts a search engine has indexed for profiles and company pages.
Available components
Last scanned (10 hours ago)
Scores higher than 79% of npm servers
Category News and Social
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 397 tokens (~397/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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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.
- 16 Oct 26 0
- Stability: 0.93 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 321 → 397 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.3.0 → 1.4.0 functional
- Package version: 1.3.0 → 1.3.1 functional
- 14 Oct 26 +44
- Injection markers: unverified → pass ▲ security
- Schema quality: 635 → 321 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.90 ▲ functional
- 12 Oct 26 0
- Package version: 1.2.1 → 1.3.0 functional
- Package version: 1.1.0 → 1.2.1 functional
- 7 Oct 26 −41
- Stability: 0.80 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 1.1.0 → 1.2.1 functional
- 4 Oct 26 +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.
- 3 Oct 26 −3
- Stability: pass → 0.77 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 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.
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 16 Oct 2026 · Analysed npm/@mambalabsdev/mcp-linkedin-post-engager-capture@1.4.0
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 →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
capture_linkedin_posts_and_commenters Capture LinkedIn Posts and Commenters ~397
Point it at LinkedIn person profiles or company pages and it returns the posts a search engine has indexed for each one, as flat rows: permalink, author, a text excerpt, and the publish date decoded from the post id. No request is sent to LinkedIn and no cookie or account is used. A result counts only when its permalink names the source, so posts are never attributed to the wrong author. Coverage is what the search index holds: posts appear days or weeks after publishing and many never appear. Commenters, reaction counts, comment counts and media are no longer returned (removed 2026-10-12, they came only from LinkedIn pages). Rows carry row_type post or notice; filter on row_type before loading a table. post_id is the activity URN and is stable across runs. Every row carries degraded and degradation_reason. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| company_urls | array | – | LinkedIn company page URLs, for example https://www.linkedin.com/company/microsoft. Supply this, profile_urls, or both. |
| max_charge_usd | number | – | Optional. The actor's own spend cap for this run, in USD. The run stops before a charge would take its total past this amount, writes one notice row saying so, and keeps every row already charged. Le… |
| posted_since | string | – | ISO date or timestamp, for example 2026-08-01. Posts published before this are skipped BEFORE anything is charged. Leave empty to take everything the index holds. |
| profile_urls | array | – | LinkedIn person profile URLs, for example https://www.linkedin.com/in/williamhgates. Country subdomains such as uk.linkedin.com are fine. Supply this, company_urls, or both. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-linkedin-post-engager-capture server?
com.mambabuilt/mcp-linkedin-post-engager-capture runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-linkedin-post-engager-capture. 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-linkedin-post-engager-capture
claude mcp add com-mambabuilt-mcp-linkedin-post-engager-capture -- npx -y @mambalabsdev/mcp-linkedin-post-engager-capture
What is the com.mambabuilt/mcp-linkedin-post-engager-capture server?
com.mambabuilt/mcp-linkedin-post-engager-capture is listed in the public MCP registry as com.mambabuilt/mcp-linkedin-post-engager-capture. Collect the LinkedIn posts a search engine has indexed for profiles and company pages. This page covers its npm package (@mambalabsdev/mcp-linkedin-post-engager-capture).
Is the com.mambabuilt/mcp-linkedin-post-engager-capture server safe to use?
com.mambabuilt/mcp-linkedin-post-engager-capture scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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-post-engager-capture server expose?
com.mambabuilt/mcp-linkedin-post-engager-capture exposes 1 tool: capture_linkedin_posts_and_commenters. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-linkedin-post-engager-capture server still maintained?
com.mambabuilt/mcp-linkedin-post-engager-capture is still listed as active in the MCP registry. We last reached this channel on 16 October 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-post-engager-capture server under?
com.mambabuilt/mcp-linkedin-post-engager-capture declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.