linkedin-mcp (rugvedp/linkedin-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 5 tools. No publisher has claimed this listing.

C
Caution
74/100

linkedin-mcp

A powerful LinkedIn Profile Analyzer that seamlessly integrates with Claude AI to fetch and analyze public LinkedIn profiles, enabling users to extract, search, and analyze posts data through RapidAPI's LinkedIn Data API.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

rugvedp

Source: ModelScope

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: RAPIDAPI_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — fetch_and_save_linkedin_posts (line 50: with open(DATA_FILE, "w", encoding="utf-8") as f:)
🔐
You'll be asked for 1 credential: RAPIDAPI_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes5 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

fetch_and_save_linkedin_posts

Fetch LinkedIn posts for a given username and save them in a JSON file.

get_saved_posts

Retrieve saved LinkedIn posts with pagination. Args: start (int): Index of the first post to retrieve. limit (int): Number of posts to return (Max: 5). Returns: dict: Contains retrieved posts and a flag for more data availability.

search_posts

Search saved LinkedIn posts for a specific keyword. Args: keyword (str): The keyword to search for in post text. Returns: dict: List of posts matching the keyword.

get_top_posts

Get the top LinkedIn posts based on a specific engagement metric.

get_posts_by_date

Retrieve posts within a specified date range.

// 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.
🔐 secretRAPIDAPI_KEYyour_rapidapi_key_here
// 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

5/5 tools missing one or more hints — fetch_and_save_linkedin_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_saved_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — fetch_and_save_linkedin_posts (line 50: with open(DATA_FILE, "w", encoding="utf-8") as f:)

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

fetch_and_save_linkedin_posts: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 5 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 Verified](https://m8ven.ai/badge/mcp/rugvedp/linkedin-mcp?variant=verified)](https://m8ven.ai/mcp/rugvedp/linkedin-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f32df7510072fc5372c1f37982804372461bdcea
code hash: dd8870d10b2d069d0625ee49c6acb95287b946232e3623b76b4e247993e52146
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