LinkedIn Sales Navigator
PYPI · LINKEDIN-SALES-NAV-MCP
LinkedIn Sales Navigator contact and account search from your logged-in browser.
Available components
Last scanned (18 hours ago)
Scores higher than 99% of PyPI servers
Category CRM and Sales
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to nick-choudhary/linkedin-sales-nav-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 75 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 914 tokens (~130/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 19 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/linkedin-sales-nav-mcp@1.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | nick-choudhary/linkedin-sales-nav-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/nick-choudhary/linkedin-sales-nav-mcp/.github/workflows/publish.yml@refs/tags/v1.2.0 |
| Rekor log index | 2532458161 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8db1e7e4b33ea6a153d3ee2923bea17566fea5b1075d3cc4c6f84b2475810427 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_session_status Check Session Status ~65
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
export_results Export Results ~98
Export a saved query's records to files under the output folder.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The query's url_hash (from list_queries) or its original search URL. |
Structured output declared, but exposes no named fields.
No examples provided.
get_results Get Results Sample ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (1-200, default 25). |
| offset | integer | – | Records to skip (for paging through the sample). |
| url_or_hash | string | yes | The query's url_hash or original search URL. |
Structured output declared, but exposes no named fields.
No examples provided.
list_queries List Saved Queries ~16
List every saved search and its progress.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_accounts Search Sales Navigator Accounts ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Full Sales Navigator URL (/sales/search/accounts, /sales/search/company, or /sales/lists/accounts). |
Structured output declared, but exposes no named fields.
No examples provided.
search_contacts Search Sales Navigator Contacts ~306
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Full Sales Navigator URL (/sales/search/people, /sales/search/leads, or /sales/lists/people). |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · linkedin-sales-nav-mcp
claude mcp add nick-choudhary-linkedin-sales-nav-mcp -- uvx linkedin-sales-nav-mcp
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 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 864 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 4 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 LinkedIn Sales Navigator MCP server under?
LinkedIn Sales Navigator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.