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.
npx agentmods add mcp/styfinity/linkedin-engine/linkedin-engine-cligit clone --depth 1 https://github.com/styfinity/linkedin-engineGrade A, and why
linkedin-engine-cli 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 yesterday.
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
{ "linkedin-engine-cli": { "command": "npx", "args": [ "-y", "@styfinity/linkedin-engine-cli" ] } }
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.
- yesterday First seen · 9 lines scan A b52811a95ab2
linkedin-engine-cli is an MCP server published in the GitHub repository styfinity/linkedin-engine (7 stars, last pushed 2mo 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
tapac-mcp
MCP server "tapac-mcp" as configured in axelfreeman/tapac-mcp. Runs locally from the tapac-mcp Python package.
sales-navigator
MCP server that gives AI assistants access to LinkedIn Sales Navigator contact and account search. Runs locally from the linkedin-sales-nav-mcp Python package.
linkedin-sales-nav-mcp
MCP server that gives AI assistants access to LinkedIn Sales Navigator contact and account search. Runs locally from the linkedin-sales-nav-mcp Python package.
speed-to-lead-agent
MCP server "speed-to-lead-agent" as configured in OmateLabs/speed-to-lead-agent. Runs locally from the speed-to-lead-agent Python package.
linkednav-mcp
Run LinkedIn outreach from your AI chat: find leads, launch campaigns, send, and reply. Remote server at mcp.linkednav.com.
publiar
MCP server "publiar" as configured in TokDar2410621/publiar-mcp. Launched with publiar-mcp. Needs 2 environment variables to run.