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/prakharagarwal-dev/linkedin-mcp-serverWrote 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/prakharagarwal-dev/linkedin-mcp-server/linkedin-mcp-server)<a href="https://agentmods.dev/mcp/prakharagarwal-dev/linkedin-mcp-server/linkedin-mcp-server"><img src="https://agentmods.dev/badge/mcp/prakharagarwal-dev/linkedin-mcp-server/linkedin-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
linkedin-mcp-server 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 7d 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
{
"linkedin-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/prakharagarwal-dev/linkedin-mcp-server:0.16.0"
],
"env": {}
}
}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.
- 7d ago First seen · 12 lines scan A 62dfdc05b272
linkedin-mcp-server is an MCP server published in the GitHub repository prakharagarwal-dev/linkedin-mcp-server (2 stars, last pushed 7d ago), licensed Apache-2.0. 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
opencut-controller
Professional MCP server for video editing automation with OpenCut. Runs locally from the opencut-controller npm package.
adobe-firefly-mcp
Local MCP server that drives Adobe Firefly through a persistent Playwright browser session. Runs locally from the adobe-firefly-mcp npm package.
linkedin-mcp-pro
MCP server "linkedin-mcp-pro" as configured in horizonbymuneeb/linkedin-mcp-pro. Runs locally from the linkedin-mcp-pro Python package.
tokenhub-mcp
A token-disciplined developer MCP hub with a tiny always-loaded surface and deferred internal capabilities. Runs locally from the tokenhub-mcp npm package.
linkedin-company-admin-mcp
MCP server for LinkedIn Company Page administration - read analytics, manage posts, edit page details, grow followers. Includes personal->company bridge tools for employee advocacy. Runs locally from the linkedin-company-admin-mcp Python package.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.