# LinkedIn Sales Navigator (pypi · linkedin-sales-nav-mcp)

LinkedIn Sales Navigator contact and account search from your logged-in browser.

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `linkedin-sales-nav-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/nick-choudhary-linkedin-sales-nav-mcp/linkedin-sales-nav-mcp.md), [page](https://verifymcp.io/servers/nick-choudhary-linkedin-sales-nav-mcp/linkedin-sales-nav-mcp)

## Channel facts

- Registry: `pypi`
- Package: `linkedin-sales-nav-mcp`
- Version: `1.2.0`
- 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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 18 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 30 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 991 tokens (~141/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the LinkedIn Sales Navigator MCP server?

LinkedIn Sales Navigator runs locally as a PyPI package, launched with uvx linkedin-sales-nav-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 nick-choudhary-linkedin-sales-nav-mcp -- uvx linkedin-sales-nav-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "nick-choudhary-linkedin-sales-nav-mcp": {
      "command": "uvx",
      "args": [
        "linkedin-sales-nav-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nick-choudhary-linkedin-sales-nav-mcp": {
      "command": "uvx",
      "args": [
        "linkedin-sales-nav-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nick-choudhary-linkedin-sales-nav-mcp -- uvx linkedin-sales-nav-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nick-choudhary-linkedin-sales-nav-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "linkedin-sales-nav-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nick-choudhary-linkedin-sales-nav-mcp --command uvx --arg linkedin-sales-nav-mcp
```

### Hermes

```yaml
mcp_servers:
  nick-choudhary-linkedin-sales-nav-mcp:
    command: "uvx"
    args: ["linkedin-sales-nav-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "nick-choudhary-linkedin-sales-nav-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "linkedin-sales-nav-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add nick-choudhary-linkedin-sales-nav-mcp -t stdio -c uvx -a linkedin-sales-nav-mcp
```

### Other

```json
{
  "mcpServers": {
    "nick-choudhary-linkedin-sales-nav-mcp": {
      "command": "uvx",
      "args": [
        "linkedin-sales-nav-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-09-20 (score 81, −3)

- [functional] Stability: pass → 0.80

### 2026-09-19 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 67, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-12 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 65, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (6)

### `search_contacts` (~306 tokens)

Search Sales Navigator Contacts

Search people/leads by driving Sales Navigator in the logged-in
browser and capturing its search API responses. Results are saved to
the local database automatically; this tool returns a small summary,
not the records (call export_results or get_results for the data).

Build the search in Sales Navigator (title / geography / industry /
seniority / keyword filters), copy the URL from the address bar, and
pass it here. Saved lead lists work too.

Resumable: the search URL is hashed to a query id. If a previous run
stopped partway, calling again with the same URL resumes from the next
page instead of restarting — safe to call repeatedly to page deeper.

Input parameters:

- `include_raw` (boolean): Keep LinkedIn's raw element JSON alongside each record (useful when a field looks wrong).
- `pages` (integer): How many 25-result pages to fetch in THIS call (1-10). Call again to continue past that.
- `refresh` (boolean): If true, forget this query's saved progress and records and re-scrape from page 1.
- `resume` (boolean): If true (default), continue from where a prior run of this same URL stopped. If false, start from page 1 (records already saved are kept and de-duplicated).
- `search_url` (string, required): Full Sales Navigator URL (/sales/search/people, /sales/search/leads, or /sales/lists/people).

### `search_accounts` (~274 tokens)

Search Sales Navigator Accounts

Search companies/accounts by driving Sales Navigator in the logged-in
browser and capturing its search API responses. Results are saved to
the local database automatically; this tool returns a small summary,
not the records (call export_results or get_results for the data).

Build the search in Sales Navigator (industry / headcount / geography /
growth filters), copy the URL from the address bar, and pass it here.
Saved account lists work too.

Resumable: the search URL is hashed to a query id. If a previous run
stopped partway, calling again with the same URL resumes from the next
page instead of restarting.

Input parameters:

- `include_raw` (boolean): Keep LinkedIn's raw element JSON alongside each record.
- `pages` (integer): How many 25-result pages to fetch in THIS call (1-10).
- `refresh` (boolean): If true, forget this query's saved progress and records and re-scrape from page 1.
- `resume` (boolean): If true (default), continue from where a prior run of this same URL stopped. If false, start from page 1 (saved records are kept and de-duplicated).
- `search_url` (string, required): Full Sales Navigator URL (/sales/search/accounts, /sales/search/company, or /sales/lists/accounts).

### `list_queries` (~69 tokens)

List Saved Queries

List every saved search and its progress.

Returns:
    Dict with `queries`: for each, url_hash, url, scraper_type, status
    (new|in_progress|paused|complete), last_page, total_available,
    records_count. Use a url_hash with export_results or get_results.

### `export_results` (~98 tokens)

Export Results

Export a saved query's records to files under the output folder.

Input parameters:

- `format` (string): 'json', 'csv', or 'both' (default). JSON is the full store view; CSV is flat columns for spreadsheets.
- `include_raw` (boolean): Include LinkedIn's raw element JSON in the export.
- `url_or_hash` (string, required): The query's url_hash (from list_queries) or its original search URL.

### `get_results` (~105 tokens)

Get Results Sample

Pull a bounded slice of a saved query's records into the conversation
for analysis. Bounded on purpose — for large sets, prefer export_results
and analyze the file with code rather than loading everything into
context.

Input parameters:

- `limit` (integer): Max records to return (1-200, default 25).
- `offset` (integer): Records to skip (for paging through the sample).
- `url_or_hash` (string, required): The query's url_hash or original search URL.

### `check_session_status` (~89 tokens)

Check Session Status

Check whether the browser profile has a live Sales Navigator session.

Launches (or reuses) the browser and verifies it lands on a signed-in
/sales page. Use this first when searches fail — it tells you if you
need to run `--login` again.

Returns:
    Dict with logged_in (bool), plus the profile directory and
    headless setting for this server.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/nick-choudhary-linkedin-sales-nav-mcp/linkedin-sales-nav-mcp#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 67
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 65
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 76
- 2026-09-01: 76
- 2026-08-31: 75
- 2026-08-30: 75
- 2026-08-29: 74
- 2026-08-28: 74
- 2026-08-27: 73
- 2026-08-26: 70
- 2026-08-25: 69
- 2026-08-24: 69
- 2026-08-23: 69
- 2026-08-22: 69

## Common questions

### What is the LinkedIn Sales Navigator MCP server?

LinkedIn Sales Navigator is an MCP server listed in the public MCP registry as io.github.nick-choudhary/linkedin-sales-nav-mcp. LinkedIn Sales Navigator contact and account search from your logged-in browser. This page covers its PyPI package (linkedin-sales-nav-mcp).

### Is the LinkedIn Sales Navigator MCP server safe to use?

LinkedIn Sales Navigator scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 LinkedIn Sales Navigator MCP server expose?

LinkedIn Sales Navigator exposes 6 tools: search_contacts, search_accounts, list_queries, export_results, get_results, check_session_status. Their descriptions and schemas cost roughly 941 tokens of context every time the server is loaded.

### Is the LinkedIn Sales Navigator MCP server still maintained?

LinkedIn Sales Navigator is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/linkedin-sales-nav-mcp/
- Socket report: https://socket.dev/pypi/package/linkedin-sales-nav-mcp
- Repository: https://github.com/nick-choudhary/linkedin-sales-nav-mcp
- Changelog RSS feed: https://verifymcp.io/servers/nick-choudhary-linkedin-sales-nav-mcp/linkedin-sales-nav-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nick-choudhary-linkedin-sales-nav-mcp/linkedin-sales-nav-mcp.json
- HTML version of this page: https://verifymcp.io/servers/nick-choudhary-linkedin-sales-nav-mcp/linkedin-sales-nav-mcp