com.mambabuilt/mcp-linkedin-post-engager-capture
mamba-linkedin-post-engager-capture
Collect the LinkedIn posts a search engine has indexed for profiles and company pages.
alive probed 2026-10-19
1tools
≈ 448tokens, estimate
≈ 0.2 %of Claude's 200k window
0.3×the median server
424 msto initialize
12 msto list tools
- Run it
- npx -y @mambalabsdev/mcp-linkedin-post-engager-capture@1.4.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- mamba-linkedin-post-engager-capture 1.4.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- ≈ <0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/mambalabsdev/mcp-linkedin-post-engager-capture
- Registry
- active, updated 2026-10-16 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| capture_linkedin_posts_and_commenters | 448 | 100 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.