# com.mambabuilt/mcp-linkedin-post-engager-capture (npm · @mambalabsdev/mcp-linkedin-post-engager-capture)

Track LinkedIn posts from profiles and company pages, with the commenters LinkedIn shows publicly.

- Trust score: 65/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- npm · `@mambalabsdev/mcp-linkedin-post-engager-capture`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-post-engager-capture/mambalabsdev-mcp-linkedin-post-engager-capture.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-post-engager-capture/mambalabsdev-mcp-linkedin-post-engager-capture)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-linkedin-post-engager-capture`
- Version: `1.0.1`
- 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-08-20.

- **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.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 635 tokens (~635/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**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add com-mambabuilt-mcp-linkedin-post-engager-capture -- npx -y @mambalabsdev/mcp-linkedin-post-engager-capture
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-linkedin-post-engager-capture -- npx -y @mambalabsdev/mcp-linkedin-post-engager-capture
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-linkedin-post-engager-capture": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-linkedin-post-engager-capture"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-linkedin-post-engager-capture --command npx --arg -y --arg @mambalabsdev/mcp-linkedin-post-engager-capture
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-linkedin-post-engager-capture:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-linkedin-post-engager-capture"]
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-linkedin-post-engager-capture": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-linkedin-post-engager-capture"
      ]
    }
  }
}
```

## 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-08-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-13 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 1.0.0 → 1.0.1

### 2026-08-12 (score 61)

First indexed and scored.

## MCP tools (1)

### `capture_linkedin_posts_and_commenters` (~635 tokens)

Capture LinkedIn Posts and Commenters

Point it at LinkedIn person profiles or company pages and it returns their recent posts as flat rows, with the real reaction and comment counts on every one, plus the commenters LinkedIn shows publicly. No cookies, no LinkedIn account, no credentials of any kind. One dataset carries three row types told apart by row_type: post, engager and notice, so filter on row_type before loading a table. post_id is the numeric activity URN and is stable across runs and across both permalink spellings, which makes it safe as a primary key and as a have-I-already-seen-this check. Read the limits before relying on the commenters: LinkedIn renders about ten top-level comments to a logged-out visitor whatever the real total, measured whole-run coverage was 3.7 percent, and roughly 30 percent of comment rows carry no timestamp. Reactor identities are not served to a logged-out visitor at all, so every post row carries the real reaction_count and reactors_status says unavailable_without_login. Every row carries degraded and degradation_reason: filter on degraded before you trust an absence. Requires an APIFY_TOKEN and consumes Apify credits. Read only.

Input parameters:

- `collect_commenters` (boolean): Return one row per person who commented, with name, profile URL, comment text and comment likes. Turn it off to collect posts only, in which case commenters_collected comes back null rather than 0, b…
- `collect_reactors` (boolean): LinkedIn serves no reactor identities to a logged-out visitor, so this returns no reaction rows whatever you set. It exists so the limit is visible rather than silent, and it adds one notice row per…
- `company_urls` (array): LinkedIn company page URLs whose recent posts you want, for example https://www.linkedin.com/company/microsoft. Supply this, profile_urls, or both.
- `max_engagers_per_post` (integer): Caps the engager rows charged per post. LinkedIn shows about ten comments to a logged-out visitor, so ten is the platform ceiling and raising this above ten does nothing. Set it to 0 to pay for posts…
- `posted_since` (string): ISO date or timestamp, for example 2026-08-01. Posts published before this are skipped BEFORE anything is charged, so a scheduled run that finds nothing new costs the actor start and nothing else. Le…
- `profile_urls` (array): LinkedIn person profile URLs whose recent posts you want, for example https://www.linkedin.com/in/williamhgates. Country subdomains such as uk.linkedin.com are fine. Supply this, company_urls, or bot…
- `use_residential_proxy` (boolean): Off by default, which is what the pricing assumes and what was measured. Turn it on only if LinkedIn starts refusing the platform's datacenter addresses. Apify bills residential bandwidth on top of t…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-post-engager-capture/mambalabsdev-mcp-linkedin-post-engager-capture#diagnostics

## Score history

- 2026-08-20: 65
- 2026-08-19: 64
- 2026-08-18: 64
- 2026-08-17: 63
- 2026-08-16: 63
- 2026-08-15: 62
- 2026-08-14: 62
- 2026-08-13: 61
- 2026-08-12: 61

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-linkedin-post-engager-capture
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-linkedin-post-engager-capture
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-post-engager-capture/mambalabsdev-mcp-linkedin-post-engager-capture.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-post-engager-capture/mambalabsdev-mcp-linkedin-post-engager-capture.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-linkedin-post-engager-capture/mambalabsdev-mcp-linkedin-post-engager-capture