Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add devag7/linkedin-mcp/plugin install linkedin-mcp-localInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/devag7/linkedin-mcp/claude-plugin-linkedin-mcp-local)<a href="https://agentmods.dev/mcp/devag7/linkedin-mcp/claude-plugin-linkedin-mcp-local"><img src="https://agentmods.dev/badge/mcp/devag7/linkedin-mcp/claude-plugin-linkedin-mcp-local/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/devag7/linkedin-mcp/claude-plugin-linkedin-mcp-local"><img src="https://agentmods.dev/badge/mcp/devag7/linkedin-mcp/claude-plugin-linkedin-mcp-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
linkedin-mcp-local 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 2d 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-local": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/node_modules/linkedin-mcp-tools/dist/index.js"
],
"env": {
"LINKEDIN_ENABLE_WRITES": "false"
}
}
}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.
- 2d ago First seen · 11 lines scan A f1d6aafe98f3
linkedin-mcp-local is an MCP server published in the GitHub repository devag7/linkedin-mcp (12 stars, last pushed 2d 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-10-27.
Other mcp servers, from other repositories
server
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup. Remote server at calendarmcp.ai.
mcp-server
Cross-border debt collection: submit and track cases handled by local partners in 183 countries. Remote server at mcp.debitura.com.
neurodock-mcp-chronometric
NeuroDock chronometric MCP server — time, idle, and break management. Runs locally from the neurodock-mcp-chronometric Python package.
kenotex-mcp
Let your coding agent manage real todos, events, and check-in habits in Kenotex on your Mac. Runs locally from the kenotex-mcp npm package. Needs 2 environment variables to run.
mcp
Build, version, review, and export websites, web apps, and games from a conversation. Remote server at 2ools.app.
mcp
Provision Postgres databases + webhooks from AI coding agents in one HTTP call. Runs locally from the @instanode/mcp npm package. Needs 2 environment variables to run.