# io.github.Ruthvik-Bandari/linkedin-profile-mcp (npm · linkedin-profile-mcp)

Review and improve LinkedIn profile text the way recruiters search. No scraping or login.

- Trust score: 73/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `linkedin-profile-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/ruthvik-bandari-linkedin-profile-mcp/linkedin-profile-mcp.md), [page](https://verifymcp.io/servers/ruthvik-bandari-linkedin-profile-mcp/linkedin-profile-mcp)

## Channel facts

- Registry: `npm`
- Package: `linkedin-profile-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1348 tokens (~168/item across 8 items; 6 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.Ruthvik-Bandari/linkedin-profile-mcp server?

io.github.Ruthvik-Bandari/linkedin-profile-mcp runs locally as an npm package, launched with npx -y linkedin-profile-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ruthvik-bandari-linkedin-profile-mcp -- npx -y linkedin-profile-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ruthvik-bandari-linkedin-profile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-profile-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ruthvik-bandari-linkedin-profile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-profile-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ruthvik-bandari-linkedin-profile-mcp -- npx -y linkedin-profile-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ruthvik-bandari-linkedin-profile-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "linkedin-profile-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ruthvik-bandari-linkedin-profile-mcp --command npx --arg -y --arg linkedin-profile-mcp
```

### Hermes

```yaml
mcp_servers:
  ruthvik-bandari-linkedin-profile-mcp:
    command: "npx"
    args: ["-y", "linkedin-profile-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ruthvik-bandari-linkedin-profile-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "linkedin-profile-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ruthvik-bandari-linkedin-profile-mcp -t stdio -c npx -a -y linkedin-profile-mcp
```

### Other

```json
{
  "mcpServers": {
    "ruthvik-bandari-linkedin-profile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-profile-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 73, +6)

- [functional improvement] Stability: unverified → 0.37

### 2026-11-09 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-08 (score 52)

First indexed and scored.

## MCP tools (6)

### `get_guidelines` (~129 tokens)

Get LinkedIn guidelines

Return LinkedIn profile writing guidelines based on how technical recruiters search. Use this before drafting or rewriting a section; it is reference text and does not check anything (use lint_field or the review_* tools to check text). Returns plain text: rules, character limits and examples for one section, or the whole guide when 'section' is omitted. Read-only, no network.

Input parameters:

- `section` (string): Which section to return, e.g. 'headline', 'about', 'experience', 'open_to_work', 'skills', 'checklist'. Omit to get every section in one text.

### `lint_field` (~238 tokens)

Lint a profile field

Check the text of one LinkedIn field (or a post, comment or connection note) before the user pastes it. Use for any single field; for a headline or an Experience entry prefer review_headline or review_experience, which run these checks plus structure checks. Checks the character limit, em and en dashes, stock phrases that read as AI-written, the 'it's not X, it's Y' pattern, '-' list markers and emoji, and shows the text visible before 'see more'. Returns JSON: { field, characters, limit, issues: [{ severity: 'error' | 'warn' | 'tip', message }] }; errors must be fixed, warnings should be. Read-only, no network.

Input parameters:

- `field` (string, required): Which field the text is for; this sets the limit. headline 220, about 2600, experience_title 100, experience_description 2000, featured_title ~45, featured_description ~200, post 3000, comment 1250,…
- `text` (string, required): The exact text of the field, as it would be pasted into LinkedIn

### `review_headline` (~234 tokens)

Review a headline

Review a LinkedIn headline against recruiter-search rules. Use this for headlines instead of lint_field; use review_profile to check a whole profile at once. Runs pass/fail checks: not a vague label ('Student at X', 'Aspiring'), target role in the first 60 characters, at least 150 of 220 characters used, 3 or more segments separated by '|', an 'Open to ... roles' line, and target keywords present; plus all lint_field checks. Returns JSON: { characters, limit, issues: [...], checks: [{ name, pass, detail }] }. Rewrite and call again until every check passes. Read-only, no network.

Input parameters:

- `headline` (string, required): The full headline text, up to 220 characters
- `keywords` (array): Must-have terms from target job postings, e.g. ['Python', 'RAG']. Passes when at least 2 appear. Get them from keyword_coverage.
- `target_role` (string): The job title the person wants, e.g. 'AI Engineer'. Enables the 'role in the first 60 characters' check.

### `review_experience` (~216 tokens)

Review an Experience entry

Review the description of one LinkedIn Experience entry (one role). Use it once per role; use review_profile to check every role together with the rest of the profile. Pass/fail checks: at least 300 characters, an opening line that explains the role on its own, 3 to 7 bullets, most bullets with a number, most bullets starting with an action verb, and target keywords; it also warns on duty phrasing ('responsible for', 'worked on') and runs all lint_field checks. Returns JSON: { characters, limit, issues: [...], bullets, bulletsWithNumbers, bulletsStartingWithVerb, checks: [{ name, pass, detail }] }. Read-only, no network.

Input parameters:

- `description` (string, required): The full description text of one role, up to 2,000 characters. Bullets may start with '•', '-' or '*'.
- `keywords` (array): Target terms from job postings. Passes when at least a third of them appear. Get them from keyword_coverage.

### `keyword_coverage` (~210 tokens)

Keyword coverage vs job postings

Compare a profile with target job postings. Use it first when the user has job descriptions: it finds single words and two-word phrases that recur across the postings (in at least 2 postings when 3 or more are given) and reports which ones appear in the profile. Feed the results to review_headline and review_experience as 'keywords'. Returns JSON: { covered: [{ term, inPostings, inProfile }], missing: [...], coverage: '<n> of <m> ...' }, ranked by how many postings use each term. Only suggest adding a missing term if it truly describes the person's work. Read-only, no network.

Input parameters:

- `job_descriptions` (array, required): Full text of 1 to 10 target job postings, one string per posting
- `profile_text` (string, required): Headline, About, Experience and Skills pasted together as plain text
- `top` (integer): How many recurring terms to report, 5 to 80. Default 30.

### `review_profile` (~313 tokens)

Review a whole profile

Review a whole LinkedIn profile in one call. Use it for a first full review; then use review_headline, review_experience or lint_field on single sections while rewriting. Split the user's pasted profile (for example the text of LinkedIn's 'Save to PDF') into the fields below. Runs review_headline, lint_field on About, review_experience on each role, keyword_coverage when job descriptions are given (its top 12 terms become the keywords for the other checks), and a checklist. Returns JSON: { headline, about, experiences: [{ title, company, titleLint, review }], keywordCoverage, checklist: [{ item, pass }] }. Read-only; never logs in to or scrapes LinkedIn.

Input parameters:

- `about` (string): The About section text
- `connections` (integer): Number of connections (use 500 for '500+')
- `experiences` (array): Each Experience entry, most recent first
- `featured_count` (integer): How many items are in the Featured section
- `headline` (string, required): The headline text
- `job_descriptions` (array): Full text of 1 to 10 target job postings, one string per posting
- `location` (string): The location shown on the profile, e.g. 'Boston, MA'. A country alone fails the checklist.
- `skills` (array): Every listed skill, one per item
- `target_role` (string): The job title the person wants, e.g. 'Data Scientist'

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ruthvik-bandari-linkedin-profile-mcp/linkedin-profile-mcp#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 67
- 2026-11-11: 67
- 2026-11-10: 67
- 2026-11-09: 67
- 2026-11-08: 52

## Common questions

### What is the io.github.Ruthvik-Bandari/linkedin-profile-mcp server?

io.github.Ruthvik-Bandari/linkedin-profile-mcp is listed in the public MCP registry as io.github.Ruthvik-Bandari/linkedin-profile-mcp. Review and improve LinkedIn profile text the way recruiters search. No scraping or login. This page covers its npm package (linkedin-profile-mcp).

### Is the io.github.Ruthvik-Bandari/linkedin-profile-mcp server safe to use?

io.github.Ruthvik-Bandari/linkedin-profile-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.Ruthvik-Bandari/linkedin-profile-mcp server expose?

io.github.Ruthvik-Bandari/linkedin-profile-mcp exposes 6 tools: get_guidelines, lint_field, review_headline, review_experience, keyword_coverage, review_profile. Their descriptions and schemas cost roughly 1,340 tokens of context every time the server is loaded.

### Is the io.github.Ruthvik-Bandari/linkedin-profile-mcp server still maintained?

io.github.Ruthvik-Bandari/linkedin-profile-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.Ruthvik-Bandari/linkedin-profile-mcp server under?

io.github.Ruthvik-Bandari/linkedin-profile-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.Ruthvik-Bandari/linkedin-profile-mcp server?

VerifyMCP ran 16 checks on io.github.Ruthvik-Bandari/linkedin-profile-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/linkedin-profile-mcp
- Socket report: https://socket.dev/npm/package/linkedin-profile-mcp
- Repository: https://github.com/Ruthvik-Bandari/linkedin-profile-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ruthvik-bandari-linkedin-profile-mcp/linkedin-profile-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ruthvik-bandari-linkedin-profile-mcp/linkedin-profile-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ruthvik-bandari-linkedin-profile-mcp/linkedin-profile-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ruthvik-bandari-linkedin-profile-mcp/linkedin-profile-mcp
