LinkedIn MCP Server

The materials explicitly state that no keys or environment variables are required, and there is no request for a LinkedIn token, API key, or other highly sensitive credentials; based on the available information, no clear credential leakage or abuse risk is evident.

The tool connects to the remote endpoint linkedin.run.mcp.com.ai; since its features include profile retrieval and content publishing, user inputs, post content, or query parameters may be sent to that endpoint. This egress is within the declared functionality, but the traffic is not directly to linkedin.com, so users should be aware that it may be proxied through a third-party hosted endpoint.

The system checks indicate that it executes code or starts a local process, which is a common operating pattern for MCP tools. The current materials do not show requests for system privileges beyond its stated purpose, but it should still be treated as a tool capable of local code execution.

By design, it handles LinkedIn profile data and content to be published, so it may access user-provided text and profile information returned from the remote service. The materials do not state any need for local file read/write access or access to unrelated data sources, and no obvious overbroad access is described.

It comes from an official registry and has a public source repository with updates within the last year, providing some auditability and maintenance evidence. Community adoption is modest (8 stars) and no license is declared; these are mild caution signals but not enough on their own to elevate it to high risk.