Linkedin (himanshu31shr) MCP Server
@himanshu31shr/linkedin-mcp-server
npm
v1.0.1
Source verified
Published by himanshu31shr — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for LinkedIn API integration — compatible with all major AI IDEs
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 − 3 = 97. 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 |
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 ([get_org_page_statistics]) co-exist with external-action tools ([create_comment]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [get_org_page_statistics] → sinks [create_comment]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow get_org_page_statistics → create_comment
Tools 20
Each tool and what it can reach — statically extracted from the published source.
create_commentnetwork egressget_org_page_statisticsingests untrusted inputadd_reactionno sensitive capabilitycreate_document_postno sensitive capabilitycreate_image_postno sensitive capabilitycreate_link_postno sensitive capabilitycreate_org_postno sensitive capabilitycreate_text_postno sensitive capabilitydelete_commentno sensitive capabilitydelete_org_postno sensitive capability
Show 10 more tools ↓
delete_postno sensitive capabilityget_emailno sensitive capabilityget_org_follower_statisticsno sensitive capabilityget_org_postsno sensitive capabilityget_org_share_statisticsno sensitive capabilityget_organizationno sensitive capabilityget_post_commentsno sensitive capabilityget_profileno sensitive capabilityremove_reactionno sensitive capabilityupload_imageno 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 (20 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.1 latest |
A 97/100 | 1 | 1.13.0 | 2026-09-07 |
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 @himanshu31shr/linkedin-mcp-server --onlineOther 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 Marketing & Social
Official Abyssfall game info, newsletter double opt-in, and merch reservation tools.
AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.
Google AdSense MCP Server - Monitor earnings, reports, and account health via Claude/AI
Operational empathy for technical founders + PE/VC operators navigating high-stakes B2B interactions. 28 MCP tools + CLI: ICP scoring, persona simulation, battlecards, deal classification, prospect discovery, investor matching, founder wellness, plus mark
MCP server for Bing Webmaster Tools — SEO site management, URL submission, sitemaps, stats, keywords
MCP (Model Context Protocol) server that helps AI agents use Primer Brand (@primer/react-brand) correctly when building GitHub marketing and landing pages.