updated 2026-08-12 05:02 UTC

LinkedIn MCP Server

stickerdaniel/linkedin-mcp-server

Open-source MCP server for LinkedIn. Give Claude and any MCP-compatible AI agent access to profiles, companies, jobs, an

MCP Servers Python Grade B Listed Apache-2.0
77.1/100
Rank #78 of 1283
Compare LinkedIn MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-11 · 1d ago
Recent change
New

Is LinkedIn MCP Server safe? LinkedIn MCP Server scores 77.1/100 (Grade B), ranked #78 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 88% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#8 CloakBrowser MCP — 81.7 (A) → #9 Notion MCP Server — 80.7 (A) → #11 Containers Kubernetes MCP Server — 76.5 (B) → #12 Ha MCP — 76.5 (B) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #77
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Compare with another agent Get email alerts for LinkedIn MCP Server View MCP Servers Report missing data
81.8
Activity sub-score · out of 100
#10
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
3.1k
Forks
533
Last Push
2026-08-11
yesterday
Commits (4 wk)
72
Downloads (7d)
13,037
pypi
HN mentions (30d)
—
Open Issues
47
Rank Change
=
was #78

Analysis

HVTrust Dimensions vs MCP Servers

77.1 / 100 · 100.0% confidence

LinkedIn MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
6.9 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
19.4 / 20
7.0 above avg 12.4
AdoptionLog-scaled stars · package downloads
13.9 / 20
8.1 above avg 5.8

Activity Inputs

81.8 / 100
StarsRepository reach
20.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
23.2 / 25
CommunityFork signal
12.7 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
88%
of last 100 commits verified

Is LinkedIn MCP Server safe?

Public supply-chain signals for LinkedIn MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but LinkedIn MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does LinkedIn MCP Server publish package provenance?
Yes. LinkedIn MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does LinkedIn MCP Server have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for LinkedIn MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is LinkedIn MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does LinkedIn MCP Server use?
LinkedIn MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LinkedIn MCP Server's commits signed?
88% of the last 100 commits to LinkedIn MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
LinkedIn MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain LinkedIn MCP Server?

For maintainers

HVTrust scores LinkedIn MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-08-10
Newly Listed
First tracked at rank #77
GitHub → PyPI: mcp-server-linkedin

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 77.1 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/linkedin-mcp-server.svg)](https://hvtracker.net/agents/linkedin-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/linkedin-mcp-server"><img src="https://hvtracker.net/badge/linkedin-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON