Linkedin (SARAMALI15792) MCP Server
linkedin-mcp-server
PyPI
v1.0.0
Published by saramali15792 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Model Context Protocol (MCP) server for LinkedIn - enabling AI agents to interact with LinkedIn's professional network
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([linkedin_get_my_profile, linkedin_get_member_profile]) co-exist with external-action tools ([linkedin_create_comment]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [linkedin_get_my_profile, linkedin_get_member_profile] → sinks [linkedin_create_comment]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow linkedin_get_my_profile → linkedin_create_comment
Tools 17
Each tool and what it can reach — statically extracted from the published source.
linkedin_create_commentnetwork egresslinkedin_get_member_profileingests untrusted inputlinkedin_get_my_profileingests untrusted inputlinkedin_create_image_postno sensitive capabilitylinkedin_create_postno sensitive capabilitylinkedin_delete_commentno sensitive capabilitylinkedin_delete_postno sensitive capabilitylinkedin_exchange_codeno sensitive capabilitylinkedin_get_company_profileno sensitive capabilitylinkedin_get_job_detailsno sensitive capability
Show 7 more tools ↓
linkedin_get_oauth_urlno sensitive capabilitylinkedin_get_post_commentsno sensitive capabilitylinkedin_get_recent_postsno sensitive capabilitylinkedin_search_companiesno sensitive capabilitylinkedin_search_jobsno sensitive capabilitylinkedin_search_peopleno sensitive capabilitylinkedin_update_postno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan linkedin-mcp-server --online --registry pypiOther implementations of Linkedin 20
Independent packages implementing the same tool, scanned with the same engine. Compare all 21 side by side →
LinkedIn Ads MCP Server - Campaign entity management and reporting via LinkedIn Marketing API v2
LinkedIn MCP server — publish posts, articles, and media via the LinkedIn API
MCP server for LinkedIn API via HarvestAPI - Returns cleaned data in TOON format for token efficiency
MCP server for LinkedIn — post, comment, react, and manage content via AI agents
MCP server for linkedin API integration
MCP server for posting to LinkedIn via the LinkedIn API using an OAuth access token
More in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.