Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/nick-choudhary/linkedin-sales-nav-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/nick-choudhary/linkedin-sales-nav-mcp/sales-navigator)<a href="https://agentmods.dev/mcp/nick-choudhary/linkedin-sales-nav-mcp/sales-navigator"><img src="https://agentmods.dev/badge/mcp/nick-choudhary/linkedin-sales-nav-mcp/sales-navigator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/nick-choudhary/linkedin-sales-nav-mcp/sales-navigator"><img src="https://agentmods.dev/badge/mcp/nick-choudhary/linkedin-sales-nav-mcp/sales-navigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sales-navigator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"sales-navigator": {
"command": "uv",
"args": [
"run",
"linkedin-sales-nav-mcp"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 9 lines scan A 2f0571ddfcd2
sales-navigator is an MCP server published in the GitHub repository nick-choudhary/linkedin-sales-nav-mcp (3 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
publiar
MCP server "publiar" as configured in TokDar2410621/publiar-mcp. Launched with publiar-mcp. Needs 2 environment variables to run.
linkedin-engine-cli
MCP server "linkedin-engine-cli" as configured in styfinity/linkedin-engine. Runs locally from the @styfinity/linkedin-engine-cli npm package.
linkedin-godmode
MCP server "linkedin-godmode" as configured in samihalawa/linkedin-godmode-plugin. Runs ./dist/cli.js with node.
curtis-mcp
Curtis is an MCP server that runs your LinkedIn outreach from your own machine: it logs in once, works through your contact list, and sends connection requests slowly enough to look like you. Runs locally from the curtis-mcp npm package.
linkednav-mcp
Run LinkedIn outreach from your AI chat: find leads, launch campaigns, send, and reply. Remote server at mcp.linkednav.com.
greptile
MCP server "greptile", hosted remotely at api.greptile.com, as configured in tr4m0ryp/linkedin-mcp-server.