Back to MCP Trust Indexm8ven
C
Limited view
73/100
1 month ago

LinkedIn MCP Server

A ToS-compliant Model Context Protocol server for LinkedIn that uses the official API for OAuth 2.0 authentication, profile reading, and content posting.

→ anubisalpha/linkedin-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

anubisalpha

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: LINKEDIN_MCP_ENCRYPTION_KEY, LINKEDIN_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configLINKEDIN_MCP_APPROVAL_STAMPNo Text appended to posts. Set to empty string to disable.
configLINKEDIN_MCP_AUDIT_PATHNo Custom audit log path (default: ~/.linkedin-mcp/audit.log)
configLINKEDIN_MCP_CALLBACK_PORTNo OAuth callback port (default: 8585)
configLINKEDIN_MCP_TOKEN_PATHNo Custom token storage path (default: ~/.linkedin-mcp/tokens.json)
configLINKEDIN_MCP_HISTORY_PATHNo Custom post history path (default: ~/.linkedin-mcp/history.json)
🔐 secretLINKEDIN_MCP_ENCRYPTION_KEYNo Custom encryption key for token portability between machines
configLINKEDIN_CLIENT_IDYes Your LinkedIn app's Client ID
🔐 secretLINKEDIN_CLIENT_SECRETYes Your LinkedIn app's Client Secret
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

17/17 tools missing one or more hints — linkedin_login (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); linkedin_logout (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); linkedin_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/anubisalpha-linkedin-mcp-11w7rv)](https://m8ven.ai/mcp/anubisalpha-linkedin-mcp-11w7rv)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ed4c6ba6e15e65bc85462be4b6420aa6149a2422
code hash: f1372fc7dc2f296f9f7869fe26dcb16c2291f7d843ad046ae5739913c8b8fb0f
verified: 6/24/2026, 10:11:45 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client