mcp-pulse

io.github.johnisanerd/linkedin-posts

io.github.johnisanerd/linkedin-posts

io.github.johnisanerd/linkedin-posts did not answer the probe on 2026-10-03. Result: needs auth (HTTP 401).

Scrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API.

needs auth probed 2026-10-03 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing or invalid access token. Pass an Apify API token in the 
Endpoint
https://mcp.apify.com/?tools=johnvc/linkedin-posts-api (streamable-http)
Host
mcp.apify.com
Repository
https://github.com/johnisanerd/Apify-LinkedIn-Posts-API
Website
https://apify.com/johnvc/linkedin-posts-api?fpr=9n7kx3&fp_sid=mcpregistry
Registry
active, updated 2026-07-13 · registry entry
Reachable
2 of the last 2 probes

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsTokens
2026-10-03 20:38needs auth
2026-10-03 17:54needs auth

Badge

mcp-pulse: needs auth

[![mcp-pulse](https://mcp-pulse.ulehla.dev/badge/io.github.johnisanerd/linkedin-posts.svg)](https://mcp-pulse.ulehla.dev/s/io.github.johnisanerd/linkedin-posts)